Simple questions

View: New views
4 Messages — Rating Filter:   Alert me  

Simple questions

by GyroTech :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

First off, if this isn't the place for these questions, my apologies and
it would be great if you could direct me to where they should be asked...

I am trying to build a lot of dependency packages for a library called
CEGUI (an OpenGL-based UI widget library) since they only support
various versions of VC on Windows.

My first question is how, when I'm building these libraries do I switch
to a debug build of them? They spit out static and dynamic builds just
fine, but CEGUI debugging expects debug version of various libraries. Is
there a standard argument I can pass in to make to push out a debug
build with a suffix of my choosing (for instance, running make would
produce <lib>.dll, I want it to compile a debug version as <lib>_d.dll)?
Or is it just down to the configure script??

Secondly, how can I check if they way I've got things set up is sane? I
was advised to make sure I passed in CFLAGS="-I/local/include"
LDFLAGS="-L/local/lib" INCLUDE_PATH="/local/include"
LIBRARY_PATH="/local/lib" which did clear up many problems I had with
dependencies before. But now I get a host of:
configure: WARNING: <filename> accepted by the compiler, rejected by the
preprocessor!
configure: WARNING: <filename>: proceeding with the compiler's result
which doesn't sound good :-) Then during the build process I get the
inevitable linker errors even though all the .a and .la files are where
they should be.

Any advice at all will be welcomed. Many thanks,

Gyro

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: Simple questions

by Ralf Wildenhues :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

* GyroTech wrote on Thu, Oct 22, 2009 at 10:14:23PM CEST:
> Secondly, how can I check if they way I've got things set up is sane? I
> was advised to make sure I passed in CFLAGS="-I/local/include"
> LDFLAGS="-L/local/lib" INCLUDE_PATH="/local/include"
> LIBRARY_PATH="/local/lib" which did clear up many problems I had with
> dependencies before. But now I get a host of:
> configure: WARNING: <filename> accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: <filename>: proceeding with the compiler's result

Preprocessor flags like -I and -D go in the CPPFLAGS variable, not the
CFLAGS variable.  The latter is passed to the compiler only, the former
to both the preprocessor and the compiler.  This explains the warnings
you are seeing.

> which doesn't sound good :-) Then during the build process I get the
> inevitable linker errors even though all the .a and .la files are where
> they should be.

No idea in which way your linker errors are inevitable, for that it
would help to actually see the errors.

Cheers,
Ralf

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: Simple questions

by GyroTech :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ralf Wildenhues wrote:
> Preprocessor flags like -I and -D go in the CPPFLAGS variable, not the
> CFLAGS variable.  The latter is passed to the compiler only, the former
> to both the preprocessor and the compiler.  This explains the warnings
> you are seeing.
Yup, fixing up the CPPFLAGS cleared the warnings. Thanks very much.

> No idea in which way your linker errors are inevitable, for that it
> would help to actually see the errors.
I've tried asking the DevIL (also called OpenIL) library developers but
so far have had little response.  The errors seem to occur when make
starts trying to link with the .la files of things like libjpeg and
libpng. Errors churned out below:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include/IL -I
./../src-ILUT/incl
ude -I ./../include -I/local/include -msse -msse2 -msse3
-I/local/include -MT li
bILUT_la-ilut_win32.lo -MD -MP -MF .deps/libILUT_la-ilut_win32.Tpo -c
./../src-I
LUT/src/ilut_win32.c -o libILUT_la-ilut_win32.o >/dev/null 2>&1
mv -f .deps/libILUT_la-ilut_win32.Tpo .deps/libILUT_la-ilut_win32.Plo
/bin/sh ../libtool --tag=CC   --mode=link gcc -msse -msse2 -msse3
-I/local/incl
ude -lgdi32 -lglu32 -lopengl32  -lm -lopengl32  -lm  -version-info 2:0:1
-no-und
efined -L/local/lib -o libILUT.la -rpath /usr/local/lib
libILUT_la-ilut_main.lo
libILUT_la-ilut_states.lo libILUT_la-ilut_internal.lo
libILUT_la-ilut_directx.l
o libILUT_la-ilut_directx9.lo  libILUT_la-ilut_opengl.lo
libILUT_la-ilut_win32.
lo libILU.la -lm -lz

*** Warning: This system can not link to static lib archive libILU.la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
libtool: link: warning: `/local/lib/libjpeg.la' seems to be moved

*** Warning: This system can not link to static lib archive
/c/Programming/Tools
/CEGUI/Lib-deps/devil-1.7.8/lib/libIL.la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
libtool: link: warning: `/local/lib/libjpeg.la' seems to be moved

*** Warning: This system can not link to static lib archive
/local/lib/libpng12.
la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.

*** Warning: This system can not link to static lib archive
/local/lib/libjasper
.la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.

*** Warning: linker path does not have real file for library -lz.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libz and none of the candidates passed a file format test
*** using a file magic. Last file checked:
C:/Programming/Tools/MSys1.0/local/li
b//libz.a
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
libtool: link: ar cru .libs/libILUT.a  libILUT_la-ilut_main.o
libILUT_la-ilut_st
ates.o libILUT_la-ilut_internal.o libILUT_la-ilut_directx.o
libILUT_la-ilut_dire
ctx9.o libILUT_la-ilut_opengl.o libILUT_la-ilut_win32.o
libtool: link: ranlib .libs/libILUT.a
libtool: link: ( cd ".libs" && rm -f "libILUT.la" && ln -s
"../libILUT.la" "libI
LUT.la" )
make[1]: Leaving directory
`/c/Programming/Tools/CEGUI/Lib-deps/devil-1.7.8/lib'

Making all in bin
make[1]: Entering directory
`/c/Programming/Tools/CEGUI/Lib-deps/devil-1.7.8/bin
'
gcc -DHAVE_CONFIG_H -I. -I../include/IL  -I ./../include
-I/local/include  -I/local/include -MT ilur.o -MD -MP -MF .deps/ilur.Tpo
-c -o ilur.o `test -f '../src-ILU/ilur/ilur.c' || echo
'./'`../src-ILU/ilur/ilur.c
mv -f .deps/ilur.Tpo .deps/ilur.Po
/bin/sh ../libtool --tag=CC   --mode=link gcc  -I/local/include
-L/local/lib -o ilur.exe ilur.o ../lib/libILU.la -lm -lz
libtool: link: gcc -I/local/include -o .libs/ilur.exe ilur.o
-L/local/lib ../li
b/.libs/libILU.a
/c/Programming/Tools/CEGUI/Lib-deps/devil-1.7.8/lib/.libs/libIL.a
/local/lib/libtiff.dll.a /local/lib/libpng12.a -lmng
/local/lib/liblcms.dll.a
  /local/lib/libjasper.a /usr/local/lib/libjpeg.dll.a -lz -L/local/lib
-L/usr/local/lib
ilur.o:ilur.c:(.text+0x3b): undefined reference to `_imp__iluAlienify@0'
ilur.o:ilur.c:(.text+0x108): undefined reference to `_imp__iluBlurAvg@4'
ilur.o:ilur.c:(.text+0x1d7): undefined reference to
`_imp__iluBlurGaussian@4'
ilur.o:ilur.c:(.text+0x2a6): undefined reference to
`_imp__iluBuildMipmaps@0'
ilur.o:ilur.c:(.text+0x375): undefined reference to
`_imp__iluCompareImage@4'
ilur.o:ilur.c:(.text+0x43c): undefined reference to `_imp__iluContrast@4'
ilur.o:ilur.c:(.text+0x4fb): undefined reference to `_imp__iluCrop@24'
ilur.o:ilur.c:(.text+0x5d0): undefined reference to `_imp__iluEdgeDetectE@0'
ilur.o:ilur.c:(.text+0x6a5): undefined reference to `_imp__iluEdgeDetectP@0'
ilur.o:ilur.c:(.text+0x77a): undefined reference to `_imp__iluEdgeDetectS@0'
ilur.o:ilur.c:(.text+0x83d): undefined reference to `_imp__iluEmboss@0'
ilur.o:ilur.c:(.text+0x90f): undefined reference to
`_imp__iluEnlargeCanvas@12'
ilur.o:ilur.c:(.text+0x9de): undefined reference to
`_imp__iluEnlargeImage@12'
ilur.o:ilur.c:(.text+0xaa5): undefined reference to `_imp__iluEqualize@0'
ilur.o:ilur.c:(.text+0xb7a): undefined reference to
`_imp__iluConvolution@12'
ilur.o:ilur.c:(.text+0xc44): undefined reference to `_imp__iluFlipImage@0'
ilur.o:ilur.c:(.text+0xd13): undefined reference to
`_imp__iluGammaCorrect@4'
ilur.o:ilur.c:(.text+0xde8): undefined reference to `_imp__iluInvertAlpha@0'
ilur.o:ilur.c:(.text+0xeab): undefined reference to `_imp__iluMirror@0'
ilur.o:ilur.c:(.text+0xf72): undefined reference to `_imp__iluNegative@0'
ilur.o:ilur.c:(.text+0x103f): undefined reference to `_imp__iluNoisify@4'
ilur.o:ilur.c:(.text+0x1106): undefined reference to `_imp__iluPixelize@4'
ilur.o:ilur.c:(.text+0x11d8): undefined reference to
`_imp__iluReplaceColour@16'

ilur.o:ilur.c:(.text+0x129b): undefined reference to `_imp__iluRotate@4'
ilur.o:ilur.c:(.text+0x1362): undefined reference to `_imp__iluRotate3D@16'
ilur.o:ilur.c:(.text+0x142d): undefined reference to `_imp__iluSaturate1f@4'
ilur.o:ilur.c:(.text+0x14f8): undefined reference to
`_imp__iluSaturate4f@16'
ilur.o:ilur.c:(.text+0x15ba): undefined reference to `_imp__iluScale@12'
ilur.o:ilur.c:(.text+0x1685): undefined reference to `_imp__iluScaleAlpha@4'
ilur.o:ilur.c:(.text+0x1754): undefined reference to
`_imp__iluScaleColours@12'
ilur.o:ilur.c:(.text+0x1829): undefined reference to
`_imp__iluSetLanguage@4'
ilur.o:ilur.c:(.text+0x18f6): undefined reference to `_imp__iluSharpen@8'
ilur.o:ilur.c:(.text+0x19cb): undefined reference to
`_imp__iluSwapColours@0'
ilur.o:ilur.c:(.text+0x1a8a): undefined reference to `_imp__iluWave@4'
ilur.o:ilur.c:(.text+0x2952): undefined reference to `_imp__ilGetError@0'
ilur.o:ilur.c:(.text+0x2968): undefined reference to
`_imp__iluErrorString@4'
ilur.o:ilur.c:(.text+0x2a1f): undefined reference to `_imp__ilGenImages@8'
ilur.o:ilur.c:(.text+0x2a2f): undefined reference to `_imp__ilBindImage@4'
ilur.o:ilur.c:(.text+0x2a3f): undefined reference to `_imp__ilLoadImage@4'
ilur.o:ilur.c:(.text+0x2a52): undefined reference to `_imp__ilGetError@0'
ilur.o:ilur.c:(.text+0x2a62): undefined reference to
`_imp__iluErrorString@4'
ilur.o:ilur.c:(.text+0x2aa1): undefined reference to `_imp__ilGetInteger@4'
ilur.o:ilur.c:(.text+0x2ab5): undefined reference to `_imp__ilGetInteger@4'
ilur.o:ilur.c:(.text+0x2b33): undefined reference to `_imp__ilSaveImage@4'
ilur.o:ilur.c:(.text+0x2b46): undefined reference to `_imp__ilGetError@0'
ilur.o:ilur.c:(.text+0x2b56): undefined reference to
`_imp__iluErrorString@4'
ilur.o:ilur.c:(.text+0x2b94): undefined reference to
`_imp__ilDeleteImages@8'
ilur.o:ilur.c:(.text+0x2bb4): undefined reference to
`_imp__ilDeleteImages@8'
ilur.o:ilur.c:(.text+0x2c16): undefined reference to `_imp__ilInit@0'
ilur.o:ilur.c:(.text+0x2c1d): undefined reference to `_imp__iluInit@0'
collect2: ld returned 1 exit status
make[1]: *** [ilur.exe] Error 1
make[1]: Leaving directory
`/c/Programming/Tools/CEGUI/Lib-deps/devil-1.7.8/bin'

make: *** [all-recursive] Error 1

Many thanks,

Gyro

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: Simple questions

by Ralf Wildenhues :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

* GyroTech wrote on Sat, Oct 24, 2009 at 12:21:10AM CEST:
> Ralf Wildenhues wrote:
> > No idea in which way your linker errors are inevitable, for that it
> > would help to actually see the errors.
> I've tried asking the DevIL (also called OpenIL) library developers but
> so far have had little response.  The errors seem to occur when make
> starts trying to link with the .la files of things like libjpeg and
> libpng. Errors churned out below:

This might be fixed in newer (probably only the git version of) Libtool.
Can't tell exactly without debugging the libtool func_win32_libid
function though.  If upgrading doesn't help, please feel free to report
to bug-libtool.  Thanks.

> /bin/sh ../libtool --tag=CC   --mode=link gcc -msse -msse2 -msse3
> -I/local/incl
> ude -lgdi32 -lglu32 -lopengl32  -lm -lopengl32  -lm  -version-info 2:0:1
> -no-und
> efined -L/local/lib -o libILUT.la -rpath /usr/local/lib
> libILUT_la-ilut_main.lo
> libILUT_la-ilut_states.lo libILUT_la-ilut_internal.lo
> libILUT_la-ilut_directx.l
> o libILUT_la-ilut_directx9.lo  libILUT_la-ilut_opengl.lo
> libILUT_la-ilut_win32.
> lo libILU.la -lm -lz
>
> *** Warning: This system can not link to static lib archive libILU.la.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.

Cheers,
Ralf

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users