Hi!
2009/5/27 jean-luc malet :
> with theses what is the difference between -lopengl32 and -lGL?
Actualliy don't know. But previously proposed solution works. That's
was enough for me.
Thanks.
---
/vap/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
jean-luc malet wrote:
> I never managed to build something that link against those libs. if
> you strip the "32" at the end of each libs it shall work
> ie use :
> lglut -lglu -lGL
> however I don't know but every package that use autotools try to link
> with theses what is the difference be
On Tue, May 26, 2009 at 8:33 PM, Vladimir A. Petrov wrote:
> Andre,
>
>> The correct order for searching the libraries is: -lglut32 -lglu32 -lopengl32
>>
>> fly-cubes.c must be _before_ the libraries. Chuck's response was correct
>> about this last point,
>> but wrong about the librairies order.
Andre,
> The correct order for searching the libraries is: -lglut32 -lglu32 -lopengl32
>
> fly-cubes.c must be _before_ the libraries. Chuck's response was correct
> about this last point,
> but wrong about the librairies order.
Thank you for your clarification.
---
/vap/
--
Unsubscribe info:
"Vladimir A. Petrov" wrote:
> Hello!
Hello Vladimir,
> ...
>
> The similar problem is also reproducible at the another PC with
> different Cygwin installation and with different set of libraries
> (opengl-1.1.0-10 and freeglut-2.4.0-1) that in this case are part of
> the Cygwin distributio
Vladimir A. Petrov wrote:
>> with embedded spaces because they subject them to unquoted shell handling,
>> which treats the space as a word-separator. So, it's not "worse", but it is
>> "unusual and therefore less well tested and therefore more prone to bugs".
>
> Guys, we are talking not about g
Charles,
2009/5/24 Charles Wilson :
> Good:
> gcc -Wall -I /cygdrive/c/Program\ Files/PostgreSQL/8.2/include/ -L
> /cygdrive/c/Program\ Files/PostgreSQL/8.2/lib -o pgtest.exe
> pgtest.c -lpq
Thanks a lot! It works.
Hence problem is closed.
---
/vap/
--
Unsubscribe info: http://cygwin.com/
Vladimir A. Petrov wrote:
> Hello!
>
> I've faced with strange static linking issue in Cygwin environment.
> Trivial C program can not be linked against PostgreSQL libpq with the
> following diagnostics:
>
> $ gcc -Wall -I /cygdrive/c/Program\ Files/PostgreSQL/8.2/include/ -L
> /cygdrive/c/Progra
> with embedded spaces because they subject them to unquoted shell handling,
> which treats the space as a word-separator. So, it's not "worse", but it is
> "unusual and therefore less well tested and therefore more prone to bugs".
Guys, we are talking not about good and bad paths, but about some
Vladimir A. Petrov wrote:
> By the way
> why "Program Files" directory is worse than others if it easily can be
> accessed by the fully qualified path? Try to say that it is strange
> enough to the PostgreSQL guys, they are decided to put their libs
> there, not I, I've just used default installeti
Tim Prince wrote:
> Vladimir A. Petrov wrote:
>
>> I've faced with strange static linking issue in Cygwin environment.
>> Trivial C program can not be linked against PostgreSQL libpq with the
>> following diagnostics:
>>
>> $ gcc -Wall -I /cygdrive/c/Program\ Files/PostgreSQL/8.2/include/ -L
>> /c
Hi, Tim,
2009/5/23 Tim Prince :
> Vladimir A. Petrov wrote:
>
> Not strange, when gnu ld depends on order of libraries for static linking.
> ld doesn't rescan libraries when new references are added after the scan.
> It's strange enough to attempt to link libraries installed under "Program
> Fil
Vladimir A. Petrov wrote:
> I've faced with strange static linking issue in Cygwin environment.
> Trivial C program can not be linked against PostgreSQL libpq with the
> following diagnostics:
>
> $ gcc -Wall -I /cygdrive/c/Program\ Files/PostgreSQL/8.2/include/ -L
> /cygdrive/c/Program\ Files/Po
13 matches
Mail list logo
