Re: [Chicken-users] CMake MSVC appears to work

[Brandon J. Van Every]

John Cowan wrote:

Brandon J. Van Every scripsit:

  

I think if you build from scratch, you'll run into the static vs. 
dyanmic clobbering problem that I just posted about.  That's what 
happened on my system.
    

I don't know what you mean by "build from scratch".  I always build
from an empty cmake directory by pointing to the pristine darcs
directory, and I pull from darcs at least daily, more often if I
see anything here on the list.  It's true that I use the existing
CMake build as the bootstrap compiler.

I wind up with the following files in /usr/local/lib:

-rw-r--r--  1 JCowan Domain Users  243206 Aug  3 13:05 /usr/local/lib/libchicken-0.dll.a
-rw-r--r--  1 JCowan Domain Users 4276124 Aug  3 13:05 /usr/local/lib/libchicken.a
lrwxrwxrwx  1 JCowan Domain Users      33 Aug  2 17:05 /usr/local/lib/libchicken.dll.a -> /usr/local/lib/libchicken-0.dll.a
-rw-r--r--  1 JCowan Domain Users  243910 Aug  3 13:05 /usr/local/lib/libuchicken-0.dll.a
-rw-r--r--  1 JCowan Domain Users 3753362 Aug  3 13:05 /usr/local/lib/libuchicken.a
lrwxrwxrwx  1 JCowan Domain Users      34 Aug  2 17:05 /usr/local/lib/libuchicken.dll.a -> /usr/local/lib/libuchicken-0.dll.a

  

Ah, lightbulb!  You don't run into the clobbering problem because chicken-0 is a different rootname from chicken.  Whereas when I do a symlink to cygchicken.dll, then I end up with libchicken.dll.a and libchicken.a.  So until CMake 2.4.4 ships, it's actually better to symlink to libchicken-0.dll.a, because the name is different.  I was running into a new problem, that Cygwin does symlinks but MSYS doesn't.

I will patch up the final cut after a dog run and lunch.  It should keep working.


Cheers,
Brandon Van Every