plib-users

Re: [Plib-users] link plib into code on mac osx

[Frederic B. <fre...@fr...>]

Bernhard Windisch wrote :

>> extern "C" {
>> #include "plib/ul.h"
>> #include "plib/sg.h"
>> }
>>
>> -Fred
>
>
> Unfortunately that doesn't work either.

I was not trying to tell you what to do, but warn you about a possible 
pitfall. You *shouldn't* have this header in an extern "C" clause 
because they
are C++. Perhaps you included them in another header that is in such a 
clause

> These headers are written using C++. For some (unknown) reason, the 
> compiler thinks that they are written in C, then tries to read them as 
> C and finally complains because he cannot understand them.

-Fred

Re: [Plib-users] link plib into code on mac osx

[Bernhard W. <bw...@ca...>]

> extern "C" {
> #include "plib/ul.h"
> #include "plib/sg.h"
> }
>
> -Fred

Unfortunately that doesn't work either.
These headers are written using C++. For some (unknown) reason, the=20
compiler thinks that they are written in C, then tries to read them as=20=

C and finally complains because he cannot understand them.

-Bernhard
>
> Bernhard Windisch a =E9crit :
>
>> Thanks for the immediate reply.
>>
>>> Bernhard Windisch wrote:
>>>
>>>> I have written a glut-application and compiled it on Mac OS X NOT=20=

>>>> using the project development tools but the g++ compiler.
>>>> Now, I decided to design the user interface using pui but even just=20=

>>>> including the headerfile without actually using anything from the=20=

>>>> library creates real problems because the (standard) g++-3.3=20
>>>> compiler doesn't recognise the plib files as C++ and is therefore=20=

>>>> not able to compile.
>>>
>>>
>>> If it isn't able to compile your application with the PLIB headers=20=

>>> in them
>>> then the problem is not how it recognises PLIB's files - but rather=20=

>>> a matter
>>> of what language it thinks the application is written in...header=20
>>> fines have
>>> to match the language of the file they are included into.
>>>
>>
>> It is completely right that the compiler doesn't recognise the=20
>> language of pu.h. The problem is that the application IS indeed=20
>> written in C++ and has been compiled using g++-3.3 without any=20
>> problems as long as I don't include the header pu.h.
>>
>>
>>> Could you send us the EXACT output from the compiler?
>>
>>
>> Sure, here it is (though only the first few lines because the problem=20=

>> becomes evident and the whole takes up about ten pages...
>>
>> chopin:~/myProgs/MePSim/puiVersion1 bernhardwindisch$ make
>> g++ -g -I/usr/include/gcc/darwin/3.3/c++ -c MePSim.C
>> In file included from /usr/include/plib/sg.h:29,
>>                  from /usr/include/plib/fnt.h:29,
>>                  from /usr/include/plib/pu.h:28,
>>                  from MePSim.C:9:
>> /usr/include/plib/ul.h: In function `void ulEndianSwap(short unsigned=20=

>> int*)':
>> /usr/include/plib/ul.h:336: error: declaration of C function `void
>>    ulEndianSwap(short unsigned int*)' conflicts with
>> /usr/include/plib/ul.h:327: error: previous declaration `void
>>    ulEndianSwap(unsigned int*)' here
>> /usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
>> /usr/include/plib/ul.h:342: error: declaration of C function `void
>>    ulEndianSwap(float*)' conflicts with
>> /usr/include/plib/ul.h:336: error: previous declaration `void
>>    ulEndianSwap(short unsigned int*)' here
>> /usr/include/plib/ul.h: In function `void ulEndianSwap(unsigned=20
>> int*)':
>> /usr/include/plib/ul.h:342: error: cannot convert `unsigned int*' to=20=

>> `float*'
>>    for argument `1' to `void ulEndianSwap(float*)'
>> /usr/include/plib/ul.h: In function `void ulEndianSwap(int*)':
>> /usr/include/plib/ul.h:343: error: declaration of C function `void
>>    ulEndianSwap(int*)' conflicts with
>> /usr/include/plib/ul.h:342: error: previous declaration `void
>>    ulEndianSwap(float*)' here
>> /usr/include/plib/ul.h: In function `void ulEndianSwap(short int*)':
>> /usr/include/plib/ul.h:344: error: declaration of C function `void
>>    ulEndianSwap(short int*)' conflicts with
>> /usr/include/plib/ul.h:343: error: previous declaration `void
>>    ulEndianSwap(int*)' here
>> /usr/include/plib/ul.h: In function `unsigned int=20
>> ulEndianLittle32(unsigned
>>    int)':
>> /usr/include/plib/ul.h:360: error: cannot convert `unsigned int*' to=20=

>> `short
>>    int*' for argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `float=20
>> ulEndianLittleFloat(float)':
>> /usr/include/plib/ul.h:369: error: cannot convert `float*' to `short=20=

>> int*' for
>>    argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `void=20
>> ulEndianLittleArray32(unsigned int*,
>>    int)':
>> /usr/include/plib/ul.h:389: error: cannot convert `unsigned int*' to=20=

>> `short
>>    int*' for argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `void=20
>> ulEndianLittleArrayFloat(float*, int)
>>    ':
>> /usr/include/plib/ul.h:399: error: cannot convert `float*' to `short=20=

>> int*' for
>>    argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `void ulEndianBigArray32(unsigned=20=

>> int*,
>>    int)':
>> /usr/include/plib/ul.h:419: error: cannot convert `unsigned int*' to=20=

>> `short
>>    int*' for argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `void=20
>> ulEndianBigArrayFloat(float*, int)':
>> /usr/include/plib/ul.h:429: error: cannot convert `float*' to `short=20=

>> int*' for
>>    argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `unsigned int=20
>> ulEndianBig32(unsigned int)':
>> /usr/include/plib/ul.h:447: error: cannot convert `unsigned int*' to=20=

>> `short
>>    int*' for argument `1' to `void ulEndianSwap(short int*)'
>> /usr/include/plib/ul.h: In function `float ulEndianBigFloat(float)':
>> /usr/include/plib/ul.h:456: error: cannot convert `float*' to `short=20=

>> int*' for
>>    argument `1' to `void ulEndianSwap(short int*)'
>> In file included from /usr/include/plib/fnt.h:29,
>>                  from /usr/include/plib/pu.h:28,
>>                  from MePSim.C:9:
>> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
>> (*)[4], const
>>    float*, const float*)':
>> /usr/include/plib/sg.h:149: error: declaration of C function `void
>>    sgMakeCoordMat4(float (*)[4], const float*, const float*)'=20
>> conflicts with
>> /usr/include/plib/sg.h:146: error: previous declaration `void
>>    sgMakeCoordMat4(float (*)[4], float, float, float, float, float,=20=

>> float)'
>>    here
>> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
>> (*)[4], const
>>    float*, const float*)':
>> /usr/include/plib/sg.h:151: error: cannot convert `const float' to=20
>> `const
>>    float*' for argument `2' to `void sgMakeCoordMat4(float (*)[4],=20
>> const
>>    float*, const float*)'
>> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
>> (*)[4], const
>>    sgCoord*)':
>> /usr/include/plib/sg.h:155: error: declaration of C function `void
>>    sgMakeCoordMat4(float (*)[4], const sgCoord*)' conflicts with
>> /usr/include/plib/sg.h:149: error: previous declaration `void
>>    sgMakeCoordMat4(float (*)[4], const float*, const float*)' here
>> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
>> (*)[4], const
>>    float*, const float*)':
>> /usr/include/plib/sg.h:156: error: cannot convert `const float*' to=20=

>> `const
>>    sgCoord*' for argument `2' to `void sgMakeCoordMat4(float (*)[4],=20=

>> const
>>    sgCoord*)'
>> .
>> .
>> .
>>
>> I would be most grateful for any suggestions. Thanks again,
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on=20
> ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give=20=

> us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out=20=

> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> plib-users mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-users

Re: [Plib-users] link plib into code on mac osx

[Frederic B. <fre...@fr...>]

Perhaps you included plib headers inside a " extern "C"  " clause, like=20
this :

extern "C" {
#include "plib/ul.h"
#include "plib/sg.h"
}

-Fred

Bernhard Windisch a =E9crit :

> Thanks for the immediate reply.
>
>> Bernhard Windisch wrote:
>>
>>> I have written a glut-application and compiled it on Mac OS X NOT=20
>>> using the project development tools but the g++ compiler.
>>> Now, I decided to design the user interface using pui but even just=20
>>> including the headerfile without actually using anything from the=20
>>> library creates real problems because the (standard) g++-3.3=20
>>> compiler doesn't recognise the plib files as C++ and is therefore=20
>>> not able to compile.
>>
>>
>> If it isn't able to compile your application with the PLIB headers in=20
>> them
>> then the problem is not how it recognises PLIB's files - but rather a=20
>> matter
>> of what language it thinks the application is written in...header=20
>> fines have
>> to match the language of the file they are included into.
>>
>
> It is completely right that the compiler doesn't recognise the=20
> language of pu.h. The problem is that the application IS indeed=20
> written in C++ and has been compiled using g++-3.3 without any=20
> problems as long as I don't include the header pu.h.
>
>
>> Could you send us the EXACT output from the compiler?
>
>
> Sure, here it is (though only the first few lines because the problem=20
> becomes evident and the whole takes up about ten pages...
>
> chopin:~/myProgs/MePSim/puiVersion1 bernhardwindisch$ make
> g++ -g -I/usr/include/gcc/darwin/3.3/c++ -c MePSim.C
> In file included from /usr/include/plib/sg.h:29,
>                  from /usr/include/plib/fnt.h:29,
>                  from /usr/include/plib/pu.h:28,
>                  from MePSim.C:9:
> /usr/include/plib/ul.h: In function `void ulEndianSwap(short unsigned=20
> int*)':
> /usr/include/plib/ul.h:336: error: declaration of C function `void
>    ulEndianSwap(short unsigned int*)' conflicts with
> /usr/include/plib/ul.h:327: error: previous declaration `void
>    ulEndianSwap(unsigned int*)' here
> /usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
> /usr/include/plib/ul.h:342: error: declaration of C function `void
>    ulEndianSwap(float*)' conflicts with
> /usr/include/plib/ul.h:336: error: previous declaration `void
>    ulEndianSwap(short unsigned int*)' here
> /usr/include/plib/ul.h: In function `void ulEndianSwap(unsigned int*)':
> /usr/include/plib/ul.h:342: error: cannot convert `unsigned int*' to=20
> `float*'
>    for argument `1' to `void ulEndianSwap(float*)'
> /usr/include/plib/ul.h: In function `void ulEndianSwap(int*)':
> /usr/include/plib/ul.h:343: error: declaration of C function `void
>    ulEndianSwap(int*)' conflicts with
> /usr/include/plib/ul.h:342: error: previous declaration `void
>    ulEndianSwap(float*)' here
> /usr/include/plib/ul.h: In function `void ulEndianSwap(short int*)':
> /usr/include/plib/ul.h:344: error: declaration of C function `void
>    ulEndianSwap(short int*)' conflicts with
> /usr/include/plib/ul.h:343: error: previous declaration `void
>    ulEndianSwap(int*)' here
> /usr/include/plib/ul.h: In function `unsigned int=20
> ulEndianLittle32(unsigned
>    int)':
> /usr/include/plib/ul.h:360: error: cannot convert `unsigned int*' to=20
> `short
>    int*' for argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `float ulEndianLittleFloat(float)':
> /usr/include/plib/ul.h:369: error: cannot convert `float*' to `short=20
> int*' for
>    argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `void=20
> ulEndianLittleArray32(unsigned int*,
>    int)':
> /usr/include/plib/ul.h:389: error: cannot convert `unsigned int*' to=20
> `short
>    int*' for argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `void=20
> ulEndianLittleArrayFloat(float*, int)
>    ':
> /usr/include/plib/ul.h:399: error: cannot convert `float*' to `short=20
> int*' for
>    argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `void ulEndianBigArray32(unsigned=20
> int*,
>    int)':
> /usr/include/plib/ul.h:419: error: cannot convert `unsigned int*' to=20
> `short
>    int*' for argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `void=20
> ulEndianBigArrayFloat(float*, int)':
> /usr/include/plib/ul.h:429: error: cannot convert `float*' to `short=20
> int*' for
>    argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `unsigned int=20
> ulEndianBig32(unsigned int)':
> /usr/include/plib/ul.h:447: error: cannot convert `unsigned int*' to=20
> `short
>    int*' for argument `1' to `void ulEndianSwap(short int*)'
> /usr/include/plib/ul.h: In function `float ulEndianBigFloat(float)':
> /usr/include/plib/ul.h:456: error: cannot convert `float*' to `short=20
> int*' for
>    argument `1' to `void ulEndianSwap(short int*)'
> In file included from /usr/include/plib/fnt.h:29,
>                  from /usr/include/plib/pu.h:28,
>                  from MePSim.C:9:
> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
> (*)[4], const
>    float*, const float*)':
> /usr/include/plib/sg.h:149: error: declaration of C function `void
>    sgMakeCoordMat4(float (*)[4], const float*, const float*)'=20
> conflicts with
> /usr/include/plib/sg.h:146: error: previous declaration `void
>    sgMakeCoordMat4(float (*)[4], float, float, float, float, float,=20
> float)'
>    here
> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
> (*)[4], const
>    float*, const float*)':
> /usr/include/plib/sg.h:151: error: cannot convert `const float' to `con=
st
>    float*' for argument `2' to `void sgMakeCoordMat4(float (*)[4], cons=
t
>    float*, const float*)'
> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
> (*)[4], const
>    sgCoord*)':
> /usr/include/plib/sg.h:155: error: declaration of C function `void
>    sgMakeCoordMat4(float (*)[4], const sgCoord*)' conflicts with
> /usr/include/plib/sg.h:149: error: previous declaration `void
>    sgMakeCoordMat4(float (*)[4], const float*, const float*)' here
> /usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float=20
> (*)[4], const
>    float*, const float*)':
> /usr/include/plib/sg.h:156: error: cannot convert `const float*' to=20
> `const
>    sgCoord*' for argument `2' to `void sgMakeCoordMat4(float (*)[4],=20
> const
>    sgCoord*)'
> .
> .
> .
>
> I would be most grateful for any suggestions. Thanks again,

Re: [Plib-users] link plib into code on mac osx

[Bernhard W. <bw...@ca...>]

Thanks for the immediate reply.

> Bernhard Windisch wrote:
>> I have written a glut-application and compiled it on Mac OS X NOT 
>> using the project development tools but the g++ compiler.
>> Now, I decided to design the user interface using pui but even just 
>> including the headerfile without actually using anything from the 
>> library creates real problems because the (standard) g++-3.3 compiler 
>> doesn't recognise the plib files as C++ and is therefore not able to 
>> compile.
>
> If it isn't able to compile your application with the PLIB headers in 
> them
> then the problem is not how it recognises PLIB's files - but rather a 
> matter
> of what language it thinks the application is written in...header 
> fines have
> to match the language of the file they are included into.
>

It is completely right that the compiler doesn't recognise the language 
of pu.h. The problem is that the application IS indeed written in C++ 
and has been compiled using g++-3.3 without any problems as long as I 
don't include the header pu.h.


> Could you send us the EXACT output from the compiler?

Sure, here it is (though only the first few lines because the problem 
becomes evident and the whole takes up about ten pages...

chopin:~/myProgs/MePSim/puiVersion1 bernhardwindisch$ make
g++ -g -I/usr/include/gcc/darwin/3.3/c++ -c MePSim.C
In file included from /usr/include/plib/sg.h:29,
                  from /usr/include/plib/fnt.h:29,
                  from /usr/include/plib/pu.h:28,
                  from MePSim.C:9:
/usr/include/plib/ul.h: In function `void ulEndianSwap(short unsigned 
int*)':
/usr/include/plib/ul.h:336: error: declaration of C function `void
    ulEndianSwap(short unsigned int*)' conflicts with
/usr/include/plib/ul.h:327: error: previous declaration `void
    ulEndianSwap(unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:342: error: declaration of C function `void
    ulEndianSwap(float*)' conflicts with
/usr/include/plib/ul.h:336: error: previous declaration `void
    ulEndianSwap(short unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(unsigned int*)':
/usr/include/plib/ul.h:342: error: cannot convert `unsigned int*' to 
`float*'
    for argument `1' to `void ulEndianSwap(float*)'
/usr/include/plib/ul.h: In function `void ulEndianSwap(int*)':
/usr/include/plib/ul.h:343: error: declaration of C function `void
    ulEndianSwap(int*)' conflicts with
/usr/include/plib/ul.h:342: error: previous declaration `void
    ulEndianSwap(float*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(short int*)':
/usr/include/plib/ul.h:344: error: declaration of C function `void
    ulEndianSwap(short int*)' conflicts with
/usr/include/plib/ul.h:343: error: previous declaration `void
    ulEndianSwap(int*)' here
/usr/include/plib/ul.h: In function `unsigned int 
ulEndianLittle32(unsigned
    int)':
/usr/include/plib/ul.h:360: error: cannot convert `unsigned int*' to 
`short
    int*' for argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `float ulEndianLittleFloat(float)':
/usr/include/plib/ul.h:369: error: cannot convert `float*' to `short 
int*' for
    argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void 
ulEndianLittleArray32(unsigned int*,
    int)':
/usr/include/plib/ul.h:389: error: cannot convert `unsigned int*' to 
`short
    int*' for argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void 
ulEndianLittleArrayFloat(float*, int)
    ':
/usr/include/plib/ul.h:399: error: cannot convert `float*' to `short 
int*' for
    argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArray32(unsigned 
int*,
    int)':
/usr/include/plib/ul.h:419: error: cannot convert `unsigned int*' to 
`short
    int*' for argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArrayFloat(float*, 
int)':
/usr/include/plib/ul.h:429: error: cannot convert `float*' to `short 
int*' for
    argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `unsigned int 
ulEndianBig32(unsigned int)':
/usr/include/plib/ul.h:447: error: cannot convert `unsigned int*' to 
`short
    int*' for argument `1' to `void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `float ulEndianBigFloat(float)':
/usr/include/plib/ul.h:456: error: cannot convert `float*' to `short 
int*' for
    argument `1' to `void ulEndianSwap(short int*)'
In file included from /usr/include/plib/fnt.h:29,
                  from /usr/include/plib/pu.h:28,
                  from MePSim.C:9:
/usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float (*)[4], 
const
    float*, const float*)':
/usr/include/plib/sg.h:149: error: declaration of C function `void
    sgMakeCoordMat4(float (*)[4], const float*, const float*)' conflicts 
with
/usr/include/plib/sg.h:146: error: previous declaration `void
    sgMakeCoordMat4(float (*)[4], float, float, float, float, float, 
float)'
    here
/usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float (*)[4], 
const
    float*, const float*)':
/usr/include/plib/sg.h:151: error: cannot convert `const float' to 
`const
    float*' for argument `2' to `void sgMakeCoordMat4(float (*)[4], const
    float*, const float*)'
/usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float (*)[4], 
const
    sgCoord*)':
/usr/include/plib/sg.h:155: error: declaration of C function `void
    sgMakeCoordMat4(float (*)[4], const sgCoord*)' conflicts with
/usr/include/plib/sg.h:149: error: previous declaration `void
    sgMakeCoordMat4(float (*)[4], const float*, const float*)' here
/usr/include/plib/sg.h: In function `void sgMakeCoordMat4(float (*)[4], 
const
    float*, const float*)':
/usr/include/plib/sg.h:156: error: cannot convert `const float*' to 
`const
    sgCoord*' for argument `2' to `void sgMakeCoordMat4(float (*)[4], 
const
    sgCoord*)'
.
.
.

I would be most grateful for any suggestions. Thanks again,

Bernhard

Re: [Plib-users] link plib into code on mac osx

[Steve B. <sjb...@ai...>]

Bernhard Windisch wrote:
> I have written a glut-application and compiled it on Mac OS X NOT using 
> the project development tools but the g++ compiler.
> Now, I decided to design the user interface using pui but even just 
> including the headerfile without actually using anything from the 
> library creates real problems because the (standard) g++-3.3 compiler 
> doesn't recognise the plib files as C++ and is therefore not able to 
> compile.

If it isn't able to compile your application with the PLIB headers in them
then the problem is not how it recognises PLIB's files - but rather a matter
of what language it thinks the application is written in...header fines have
to match the language of the file they are included into.

My guess is that your application is in C and that's what the problem is.


Could you send us the EXACT output from the compiler?

---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...>    WorkEmail: <sj...@li...>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----

[Plib-users] link plib into code on mac osx

[Bernhard W. <bw...@ca...>]

I have written a glut-application and compiled it on Mac OS X NOT using =
the project development tools but the g++ compiler.
Now, I decided to design the user interface using pui but even just =
including the headerfile without actually using anything from the =
library creates real problems because the (standard) g++-3.3 compiler =
doesn't recognise the plib files as C++ and is therefore not able to =
compile.

I have seen on the mailing list that this problem has surfaced a number =
of times but couldn't find a solution apart from the suggestion of not =
using plib but compliling the code into my project. Does anyone who had =
the problem know, how to deal with it? Or any other ideas?

Thanks a lot,

Bernhard

[Plib-users] force feedback

[Mihnea G. <mga...@fr...>]

Hi,
I was wondering if plib supports force feedback.
Thanks,

Mihnea (Mike) Galeteanu
Software Developer
FreeBalance - global leaders in e-Government software
Tel: +1 613 236 5150 ext  339
Fax: +1 613 236 7785
mga...@Fr...

FreeBalance proudly welcomes Influatec to the FreeBalance family.
You can find out more at www.FreeBalance.com.

RE: [Plib-users] file selector length too small

[Norman V. <nh...@ca...>]

Clay, Bruce writes:

> I am using plib with an openGL program and ran into an error message 
> from the file selector saying the size is limited to 80 characters.  
> By modern standards that is a rather small director path.  
> I am using an version that is about a year and a half old. 
> Have there been any updates to this path length?

Bruce 

I think that you can locally change

PLIB / src / pui / pu.h

from
#define PUSTRING_MAX 80
to 
#define PUSTRING_MAX 256

safely.

Note: This probably won't get into the official sources

HTH

Norman

[Plib-users] file selector length too small

[Clay, B. <bc...@ba...>]

I am using plib with an openGL program and ran into an error message
from the file selector saying the size is limited to 80 characters.  By
modern standards that is a rather small director path.  I am using an
version that is about a year and a half old.  Have there been any
updates to this path length?

=20

Also I notice when using the file selector that we have to click on the
lower portion of the text or the line above the current position is
selected.  Have there been any updates to this problem?

=20

Bruce

RE: [Plib-users] Animation/Movies

[Adam C. <ajc...@ho...>]

http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=35

============================================================
Adam Courchesne
ajc...@ho...
"There are 10 types of people in this world, those who know binary and those 
who don't."



>From: "Mihnea Galeteanu" <mga...@fr...>
>Reply-To: pli...@li...
>To: <pli...@li...>,<pli...@li...>
>Subject: [Plib-users] Animation/Movies
>Date: Tue, 19 Oct 2004 09:56:31 -0400
>
>Hi,
>Do any of you know how to add animated textures in plib (i.e. i want to be 
>looking at a texturized surface and see it change from one texture to 
>another over time). Also, any clue on how I would be able to play something 
>like a movie on a surface or in opengl in general.
>Any help would be greatly appreciated
>
>Mihnea (Mike) Galeteanu
>Software Developer
>FreeBalance - global leaders in e-Government software
>Tel: +1 613 236 5150 ext  339
>Fax: +1 613 236 7785
>mga...@Fr...
>
>FreeBalance proudly welcomes Influatec to the FreeBalance family.
>You can find out more at www.FreeBalance.com.
>
>

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

[Plib-users] Animation/Movies

[Mihnea G. <mga...@fr...>]

Hi,
Do any of you know how to add animated textures in plib (i.e. i want to =
be looking at a texturized surface and see it change from one texture to =
another over time). Also, any clue on how I would be able to play =
something like a movie on a surface or in opengl in general.
Any help would be greatly appreciated

Mihnea (Mike) Galeteanu
Software Developer
FreeBalance - global leaders in e-Government software
Tel: +1 613 236 5150 ext  339
Fax: +1 613 236 7785
mga...@Fr...

FreeBalance proudly welcomes Influatec to the FreeBalance family.
You can find out more at www.FreeBalance.com.

[Plib-users] ssgaSky-class

[Michael W. <mic...@ti...>]

Hi Steve,
I am using ssgaSky to build the sky im my simulation.
After some weeks  and experiences I learned the following:
I you use the function 'reposition Flat' and I got good results for the
sun-position, if
I use for the parameter 'RightAscension' the azimut of the sun and for the
parameter 'Declination'
the altitude of the sun.
My suggestion is to document this in the documentation of SSG Auxiliary
Libraries.

Best regards

Michael

Re: [Plib-users] compilation

[David <boi...@ya...>]

thank you for the help. The gcc goes well. My problem was about the library in the cmd line. 'bye. ;)

"LAVIGNE,ERIC" <la...@uf...> wrote:gcc is the gnu compiler collection. You can call gcc for a variety 
of languages and it will choose the most appropriate compiler (out 
of its collection) based on the file extension. In this case, gcc 
would probably refer the job to g++.

Eric Lavigne


On Thu Sep 23 18:44:59 EDT 2004, Steve Baker 
wrote:
> 
> Oh - and you're compiling C++ - so shouldn't you be using 'g++'
> instead of 'gcc' ?
> 



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users


				
---------------------------------
Scopri Mister Yahoo! -  il fantatorneo sul calcio di Yahoo! Sport'

Re: [Plib-users] compilation

[LAVIGNE,ERIC <la...@uf...>]

gcc is the gnu compiler collection. You can call gcc for a variety 
of languages and it will choose the most appropriate compiler (out 
of its collection) based on the file extension. In this case, gcc 
would probably refer the job to g++.

Eric Lavigne


On Thu Sep 23 18:44:59 EDT 2004, Steve Baker 
<sjb...@ai...> wrote:
> 
> Oh - and you're compiling C++ - so shouldn't you be using 'g++'
> instead of 'gcc' ?
> 

Re: [Plib-users] compilation

[Steve B. <sjb...@ai...>]

David wrote:
> hi to all! I am new of this list. I have installed plib and compiled it. 
> Now I have this situation:
> 
>  $ ls /usr/include/ | grep -i pli
> plib

ls /usr/include/plib/

????

> $ gcc simple.cxx -lGL -lglut -lGLU -lm
> 
> but it doesn't find the plib/pu.h .

Seems most likely that somehow /usr/include/plib is empty or something??

What it the *exact* error message from gcc?

Oh - and you're compiling C++ - so shouldn't you be using 'g++' instead
of 'gcc' ?


-- 
---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...>    WorkEmail: <sj...@li...>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----

Re: [Plib-users] compilation

[David <boi...@ya...>]

you're right. I've seen in the Makefile and added the -lplibpu to the 
command line. Now all works. Thank you very much.

LAVIGNE,ERIC wrote:
> 
> David,
> 
> As a windows user, I can't be very specific, but here are some ideas.
> 
> 1) The command "$ gcc simple.cxx -lGL -lglut -lGLU -lm" told gcc that 
> you wanted to use opengl libraries and glut libraries. If your program 
> requires pu.h, then I think you will need the plibpu library also.
> 
> 2) You said that gcc can't find pu.h. Maybe there is a gcc argument that 
> would tell it extra places to look for include files.
> 
> 3) simple.cxx is one of the included examples, right? There should be a 
> makefile in the same directory. The easy way to compile is "$ make 
> simple". If you want to use the gcc command directly, consider studying 
> the makefile to learn how others have done it.
> 
> Welcome to plib.
> 
> Eric Lavigne
> 
> 
> On Thu Sep 23 01:38:48 EDT 2004, David <boi...@ya...> wrote:
> 
>> hi to all! I am new of this list. I have installed plib and compiled 
>> it. Now I have this situation:
>>
>>   $ ls /usr/include/ | grep -i pli
>> plib
>>
>>   $ ls /usr/lib/ | grep -i pli
>> libplibfnt.a
>> libplibjs.a
>> libplibnet.a
>> libplibpsl.a
>> libplibpu.a
>> libplibpuaux.a
>> libplibpw.a
>> libplibsg.a
>> libplibsl.a
>> libplibsm.a
>> libplibssg.a
>> libplibssgaux.a
>> libplibul.a
>>
>> I'm trying to compile some ittle examples but I am not able to do it. 
>> I use this command:
>>
>> $ gcc simple.cxx -lGL -lglut -lGLU -lm
>>
>> but it doesn't find the plib/pu.h .
>>
>> Anyone could help me?
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
>> Project Admins to receive an Apple iPod Mini FREE for your judgement on
>> who ports your project to Linux PPC the best. Sponsored by IBM.
>> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
>> _______________________________________________
>> plib-users mailing list
>> pli...@li...
>> https://lists.sourceforge.net/lists/listinfo/plib-users
>>
>>
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> plib-users mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-users
> 

Re: [Plib-users] compilation

[LAVIGNE,ERIC <la...@uf...>]

David,

As a windows user, I can't be very specific, but here are some 
ideas.

1) The command "$ gcc simple.cxx -lGL -lglut -lGLU -lm" told gcc 
that you wanted to use opengl libraries and glut libraries. If 
your program requires pu.h, then I think you will need the plibpu 
library also.

2) You said that gcc can't find pu.h. Maybe there is a gcc 
argument that would tell it extra places to look for include 
files.

3) simple.cxx is one of the included examples, right? There should 
be a makefile in the same directory. The easy way to compile is "$ 
make simple". If you want to use the gcc command directly, 
consider studying the makefile to learn how others have done it.

Welcome to plib.

Eric Lavigne


On Thu Sep 23 01:38:48 EDT 2004, David <boi...@ya...> 
wrote:

> hi to all! I am new of this list. I have installed plib and 
> compiled it. Now I have this situation:
> 
>   $ ls /usr/include/ | grep -i pli
> plib
> 
>   $ ls /usr/lib/ | grep -i pli
> libplibfnt.a
> libplibjs.a
> libplibnet.a
> libplibpsl.a
> libplibpu.a
> libplibpuaux.a
> libplibpw.a
> libplibsg.a
> libplibsl.a
> libplibsm.a
> libplibssg.a
> libplibssgaux.a
> libplibul.a
> 
> I'm trying to compile some ittle examples but I am not able to do 
> it. I use this command:
> 
> $ gcc simple.cxx -lGL -lglut -lGLU -lm
> 
> but it doesn't find the plib/pu.h .
> 
> Anyone could help me?
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 
> 170
> Project Admins to receive an Apple iPod Mini FREE for your 
> judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> plib-users mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-users
> 
> 

[Plib-users] PARTICLES BILLBOARDING

[Luca M. <luc...@li...>]

Hi,

It's about a week that I'm trying to create a particle system with=
 FlightGear. Although it works into the 
simulator, I'm not able to make=
 the particles visible from all the positions of the view (they are 
vis=
ible in some position but if the view rotates they disappear). 

How I =
could solve the problem? It's fearfully annoying the fact that I see them=
 only for a few 
seconds... 

I've set to true the flag turn_to_face, =
but it doesn't works. I've also tried to get some data from 
FlightGear =
about the position of the viewer, but I don't understand the use of GL_MO=
DELVIEW_MATRIX 
so I don't know which data I've to get (there's a lot of=
 stuff; relative position, absolute position, a view 
matrix ...).

Pl=
ease, someone could help me... 

Thanks,
Luca

[Plib-users] compilation

[David <boi...@ya...>]

hi to all! I am new of this list. I have installed plib and compiled it. 
Now I have this situation:

  $ ls /usr/include/ | grep -i pli
plib

  $ ls /usr/lib/ | grep -i pli
libplibfnt.a
libplibjs.a
libplibnet.a
libplibpsl.a
libplibpu.a
libplibpuaux.a
libplibpw.a
libplibsg.a
libplibsl.a
libplibsm.a
libplibssg.a
libplibssgaux.a
libplibul.a

I'm trying to compile some ittle examples but I am not able to do it. I 
use this command:

$ gcc simple.cxx -lGL -lglut -lGLU -lm

but it doesn't find the plib/pu.h .

Anyone could help me?

Re: [Plib-users] Decals

[Steve B. <sjb...@ai...>]

Tyler Ohlsen wrote:
> Is there somewhere in a state of a node to disable depth writing to
> allow for decals?

No - but you can use a draw callback function.

---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...>    WorkEmail: <sj...@li...>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----

[Plib-users] Decals

[Tyler O. <Tyl...@gm...>]

Is there somewhere in a state of a node to disable depth writing to
allow for decals?
This is the only way I've thought of to do decals:

glDepthMask(false);
ssgCullAndDraw(&ssgBranchObject1);
ssgCullAndDraw(&ssgBranchDecalForObject1);
glDepthMask(true);
glColorMask(false, false, false, false);
ssgCullAndDraw(&ssgBranchObject1);
glColorMask(true, true, true, true);

but this requries you to remove that object from the scene and call
ssgCullAndDraw on individual objects.  Is there another route?

Thanks,
Tyler


-- 
Tyler Ohlsen
Tyl...@gm...

[Plib-users] Re: Particles & billboarding

[Juhana S. <ko...@ni...>]

>From: Steve Baker <sjb...@ai...>
>
>> In this case, the generator would be
>> in the aircraft branch and the second node would be in the root.
>
>The essence of a particle system is to keep the operations on each
>particle as simple as possible.

I don't see how it gets more complex in the two node particle system.
When a particle is generated, it is added to the second node. The second
node then executes as efficiently as the current particle node.
First node does nothing but generates the particles.

As said I'm not familiar with Plib details that much. What operations
in the above would add inefficiencies to the system?

Did you have some other solution to the problem? Or is the solution
indeed that what was described already? I looked at the screenshots,
and based on the trail length, the solution was not that inefficient
as I first understood.

Hmm... I have used two node objects earlier in texture systems.
Don't know if two node objects are generally a bad idea.

Juhana
-- 
  http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
  for developers of open source graphics software

Re: [Plib-users] Re: Particles & billboarding

[Steve B. <sjb...@ai...>]

Juhana Sadeharju wrote:

> With only one particle system, should the particles somehow be
> moved out from the aircraft branch to the root level. If that is
> not possible in Plib, then how about making a new two-piece particle
> node: one node for the particle generator and one node for where the
> particles actually pops up. In this case, the generator would be
> in the aircraft branch and the second node would be in the root.

The essence of a particle system is to keep the operations on each
particle as simple as possible.

However, if you need something more complex, it should be easy to
simply copy the existing particle system code into your application
and do whatever you need.

Adding more generality to the existing implementation is generally
undesirable.

---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...>    WorkEmail: <sj...@li...>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----

[Plib-users] Re: Particles & billboarding

[Juhana S. <ko...@ni...>]

>From: s4...@sp...
>
>at last I managed to add the particles to FlightGear and to make them
>follow the aircraft (it's not a trail made by a single Particle System
>but, instead, a trail of Particle Systems... It's a performance "eater",
>but it works).

I don't know much about Plib.

With only one particle system, should the particles somehow be
moved out from the aircraft branch to the root level. If that is
not possible in Plib, then how about making a new two-piece particle
node: one node for the particle generator and one node for where the
particles actually pops up. In this case, the generator would be
in the aircraft branch and the second node would be in the root.

Juhana
-- 
  http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
  for developers of open source graphics software

[Plib-users] ssgaSky-class, setRightAscension and setDEclination

[Michael W. <mic...@ti...>]

Hi all,
for setting the sun position I used  'setRightAscension and set Declination'
with values of longitude 50 grad and latitutde 10 grad.
The RA-value dont' influence the sun-position, the declination-value is
small and therefore the sun is always in sunset. For reposition of the sum I
used 'repositionFlat'.
What I am doing wrong ?
I also have the azimut and altitude values of the sun from my sun-programm.
May be that I have to use thes values.
Who can answer me ?

Best regards

Michael