On 17/06/15 11:56, Gaurav M. Bhandarkar wrote:
[---]
> If "not-to-build-zlib-all-the-time" is the feature wanted, can this be
> provided by things like incremental linking/compiling and not an extra
> compile time argument?

   I don't see the problem; it's literally only adding
"FOSSIL_BUILD_ZLIB=1" as an nmake command line argument.  I could make
it "FOSSIL_DONT_BUILD_ZLIB=1" instead.  Personally I think it's a little
backwards, but I buy the argument that it could be better since fossil
can't function without a zlib of some sort.  Would this be preferable?

>>  I want to have a dynamically linked fossil.exe
> OK. But please don't make dynamically linked fossil.exe as the default
> fossil distribution on windows nor the default compilation process for
> windows.

   Of course.

> Few arguments for static linking:
> http://sta.li/faq
> http://harmful.cat-v.org/Blog/2007/07/02/1_What_does_dynamic_linking_and_communism_have_in_common/
> 
> also, I think a dynamically linked fossil may require the user to install
> things like https://www.microsoft.com/en-us/download/details.aspx?id=30679
> to work.

   Just to be clear; the dynamic linking is intended only as an option.
 Static will always be the default behavior.  Not only do I not want
dynamic builds to be default, more importantly Richard would never allow
it (for good reasons).

-- 
Kind Regards,
Jan
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to