OpenSSL, and shall be probably still considered experimental. HOWEVER, beware that GNUTLS support in ELinks is not so well tested as We can't say about later versions since GNUTLS people seem to have strange taste with-gnutls configure option (assuming that you have GNUTLS 1.2.0 installed To distribute ELinks executables with HTTPS support, compile ELinks with the They like to have everything legally perfect (like the Debian people -).Īs a semi-solution to this problem, GNUTLS support was introduced if you want NOT to publish or distribute such an executable, as it's breaking GPL 2(b), if So, people who are making ELinks binaries for systems with no OpenSSL in theīase system and who decided to link OpenSSL against the ELinks binary may wish Sue you, and it's not a problem for the OpenSSL people as well, as they haveĮxplicitly told me, but you might stay on the safe side. I honestly believe that for this absurd case no ELinks copyright holder will The OpenSSL library is not part of your base system, you are VIOLATING THE GPL. !BEWARE! If you _distribute_ an ELinks executable linked with OpenSSL and Probably want them ) so just copy a to ~/.elinks, and edit theĬonfiguration part - it adds various functionality to ELinks, likeĭecompression of gzipped files or HTML code rewriting for ELinks-unfriendly There may be some useful configįile examples there, along with few support tools and some Lua scripts - you WARNING: EMX has a nasty limit on open files. Radically reduce the resulting binary size by throwing out stuff you don't like.ĭetailed discussion of reducing the executable size can be found inĬopy file links.exe somewhere to your path or create CMD file that runs Usually, even after strip, the ELinks binary can measure a lot, but you can The only supported compiler is EMX, you probably won't be able toĬonfigure under OS/2 needs to know paths to gcc, make and bash. Make another directory and run path_to_source_tree/configure from That this might not quite work right now, but we're working on fixing You canįinetune what's going to be included in the binary in the nfįile, and some really detailed tuning can be performed in src/setup.h.Īlso, a nice idea is to compile ELinks outside of the source tree (note configure -help and it'll print out a list of them. Also, you may want toĪdjust some (well, plenty of) compile-time options through. However, in some FreeBSD 3 distributions you have to You want, feel free to go ahead and update the patch for the current tree and ![]() They may not apply, since I don't update patches in contrib/ regularly - if Them, try to apply them by doing (for each one): May contain patches that are of use to you. If you want to compile ELinks, first check the directory named contrib/, it Snapshot - you don't need to do this there. Otherwise, you have to use the nightly GIT Problems, try running this first.) Also, you obviously need GNU make andĪutoconf installed on your system (for the supported versions of autoconf, autogen.sh! (It should be enough to do it once - however, if you have build Note that if you obtained the sources directly from GIT, you NEED to run To update your existing tree to the latest GIT version, do: ![]() $ git clone check_file_SITES_for_value_of_this In order to check out the latest tree from GIT: Check out the bottom of this file if you're upgrading from Links or an olderĮLinks! And be sure to look at doc/ecmascript.txt if you want (experimental)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |