On Wed, Jun 2, 2010 at 9:47 AM, Jim Michaels wrote:
> it's probably my machine, but once I execute g++ and windres, I can no
> longer execute them again. they corrupt themselves.
>
> in other words, I can't do it twice. weirdly enough, even the source zip
> file got corrupted, so I am thinking i
it's probably my machine, but once I execute g++ and windres, I can no longer
execute them again. they corrupt themselves.
in other words, I can't do it twice. weirdly enough, even the source zip file
got corrupted, so I am thinking it's probably my system. 5-year-old power
supply (maybe 2 y
it seems that this is no longer necessary. I stand corrected.
one of my points was to use a single directory for the include files and a
single directory for the lib files.
Why? it would be REALLY NICE if I could simply look in a single lib directory
for the lib file I want to include ( to
also, by doing a grep _eLut, this is the result:
hradec$ grep '_eLut'
/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/./build/mingw/ilmbase-1.0.1/lib/*
Binary file
/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/./build/mingw/ilmbase-1.0.1/lib/libHalf.a
match
On 6/2/2010 10:08, Hradec wrote:
> i686-w64-mingw32-g++
> -I/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/pthreads/build/GC_x86_4.6.0_20100528/include/
> -L/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/pthreads/build/GC_x86_4.6.0_20100528/lib/
> -I./src/inc
i686-w64-mingw32-g++
-I/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/pthreads/build/GC_x86_4.6.0_20100528/include/
-L/Volumes/Data/Users/hradec/dev/svn/cortex4all/trunk/OIIO/externals/pthreads/build/GC_x86_4.6.0_20100528/lib/
-I./src/include -DWINAPI=__stdcall -D__MINGW32__ -D_
On 6/2/2010 06:28, Hradec wrote:
> Works!! I got it linking correctly... I actually found the libtool template
> code inside configure, so it was pretty simple to delete it from there and
> now I got a proper configure patch which generates a patched libtool.
>
> Although it links correctly now, I'
Works!! I got it linking correctly... I actually found the libtool template
code inside configure, so it was pretty simple to delete it from there and
now I got a proper configure patch which generates a patched libtool.
Although it links correctly now, I'm not getting any DLLs out of it... just
.
Hi,
My ultimate goal is to port GSL to Python via SWIG. Now that I can build the
static and dynamic libraries of GSL, I think that I might be able to pull it
off. GSL is a wonderful and mature scientific library - highly recommended.
I did have issues with the configure script but that turned out
