Permalink
Show file tree
Hide file tree
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
ocamlyices2: only build the static stub using static libgmp.a.
The library libgmp.a will be searched in system dirs or you can use the flag --with-static-gmp= when running ./configure for setting your own libgmp.a. If no libgmp.a is found, the shared library is used. You can force the use of shared gmp library with --with-shared-gmp. If --with-shared-gmp is not given, the libgmp.a that has been found will be included in the list of installed files. The reason is because if we want to build a shared-gmp-free binary, zarith will sometimes pick the shared library (with -lgmp) over the static lbirary libgmp.a. Including libgmp.a in the distribution of ocamlyices2 is a convenience for creating gmp-shared-free binaries. Why do we prefer using a static version of libgmp.a? =================================================== This is because we build a non-PIC static version of libyices.a. If we wanted to build both static and shared stubs, we should either - build a PIC libyices.a but it would conflict with the non-PIC one - build a shared library libyices.so. For now, I chose to just skip the shared stubs (dllyices2_stubs.so). Also: * turn on -fPIC (in configure.ac) only if non-static gmp * added a way to link statically to libgmp.a (--with-static-gmp) * use -package instead of -I/lib for compiling *.c in ocamlc This option uses the change I made to the build system of libyices. Why? Because I want the possibility of producing binaries that do not need any dll alongside. Guess the host system and pass it to libyices ./configure ========================================================= It is now possible to use ./configure for mingw32 cross-compilation.
- Loading branch information
Showing
10 changed files
with
4,407 additions
and
126 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.