plib-users

Re: [Plib-users] Multithreading in FG

[Hemalatha S. <hem...@re...>]

 =A0=0AHi,=0AThanks for your reply.=0AWe are trying to project three views(=
center,left,right) on to three projector screens.Aircraft data(lat,lon,alt =
etc) is sent to these three systems from one system through ethernet.=0A=0A=
We need to synchronize all the three views.=0A=0AWe have tried one of the m=
echanism to synchronize.......=0A=0ABefore swapping buffers, the left and r=
ight systems send done signal to the center system.Once the center system r=
ecieves done signal from both the systems, it sends release signal to both =
the system saying that it can swap the buffers.=0ABy doing this there was s=
ome improvement seen but with some delay.=0A=0A=0APlz help me to sort out t=
his problem.=0A=0AWaiting for your reply.=0ARegards,=0AHemalatha=0A=0AOn Tu=
e, 29 Aug 2006 steve wrote :=0A>I havn't given much thought to threading al=
ternate frames - the=0A>reason being that the increase in latency is not wo=
rth the savings=0A>in frame time.  I design flight simulators for a living =
- and the=0A>fight to keep latency down is at least as important as the fig=
ht to=0A>keep frame rates up.=0A>=0A>Nothing in PLIB was ever designed for =
threading - so expect a LOT=0A>of things to break!=0A>=0A>Sadly, you are on=
 your own on this one - this is not a path I'm=0A>interested in treading - =
it's a steep and twisty path and it's=0A>leading in the wrong direction.=0A=
>=0A>Good luck!=0A>=0A>Hemalatha Sharma wrote:=0A>>   Hi,=0A>>We are using =
Flightgear version 0.9.4, in which we are trying to implement multi-threadi=
ng. In one thread, processing of next frame will be done and in the other, =
rendering of the previous frame. Here, fgMainLoop() is split into two threa=
ds, all the processing before calling fgRenderFrame() in one thread, i.e. s=
ubsystem updates, input/output updates, tile manager updates,  etc., and fg=
RenderFrame() in the other thread.=0A>>=0A>>Is this the correct method of s=
plitting processing and rendering of frame data?=0A>>=0A>>We are using the =
below to create a thread:=0A>>hThread[1] =3D CreateThread(NULL,0,(LPTHREAD_=
START_ROUTINE)fgRenderFrame1,NULL,0,&dwID[1]);=0A>>       CloseHandle(hThre=
ad[1]);=0A>>=0A>>Using the above gives us stack dump error.=0A>>=0A>>Please=
 give us a solution as to how to implement threading.=0A>>Eagerly waiting f=
or your reply.=0A

Re: [Plib-users] Multithreading in FG

[steve <sjb...@ai...>]

Stuart McDonald wrote:

> I'm not sure how you expect to get a latency drop by rendering
> alternative frames in threads. I could see putting all the rendering
> in a thread and all "logic" processing in another (since there won't
> be input from the user to process constantly). If your code is split
> right that should be doable.

Right - physics, audio and AI in one thread - graphics in another.
(Although even doing physics in parallel hits latency unless you are
quite clever about it).

Re: [Plib-users] Multithreading in FG

[Stuart M. <stu...@bl...>]

Steve makes a good point. I hadn't actually looked at what you
are threading. Areas where I use threading are where I'm going
to get blocking. So reading and writing to/from the socket are
threaded. It does introduce problems, but for networked programs,
if you do it right, threads are the way to go.

BTW I've not used threads with PLIB (I only use the netSocket
class from PLIB), so I'm not sure what problems that will introduce
on top of threads themselves.

I'm not sure how you expect to get a latency drop by rendering
alternative frames in threads. I could see putting all the rendering
in a thread and all "logic" processing in another (since there won't
be input from the user to process constantly). If your code is split
right that should be doable.

I try to write as though the logic code knows nothing about the
display code. So in theory you can drop in new rendering code (say
for text only logging output) without changing anything else.

Given the amount of problems threading introduces I'd make very
sure you need the boost and that it will actually give you that
boost.


--Stuart.


-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of steve
Sent: Monday, August 28, 2006 10:42 PM
To: Hemalatha Sharma; PLIB Users
Cc: fli...@fl...;
fli...@li...;
pli...@li...;
fli...@fl...
Subject: Re: [Plib-users] Multithreading in FG

I havn't given much thought to threading alternate frames - the
reason being that the increase in latency is not worth the savings
in frame time.  I design flight simulators for a living - and the
fight to keep latency down is at least as important as the fight to
keep frame rates up.

Nothing in PLIB was ever designed for threading - so expect a LOT
of things to break!

Sadly, you are on your own on this one - this is not a path I'm
interested in treading - it's a steep and twisty path and it's
leading in the wrong direction.

Good luck!

Re: [Plib-users] Multithreading in FG

[steve <sjb...@ai...>]

I havn't given much thought to threading alternate frames - the
reason being that the increase in latency is not worth the savings
in frame time.  I design flight simulators for a living - and the
fight to keep latency down is at least as important as the fight to
keep frame rates up.

Nothing in PLIB was ever designed for threading - so expect a LOT
of things to break!

Sadly, you are on your own on this one - this is not a path I'm
interested in treading - it's a steep and twisty path and it's
leading in the wrong direction.

Good luck!

Hemalatha Sharma wrote:
>   Hi,
> We are using Flightgear version 0.9.4, in which we are trying to 
> implement multi-threading. In one thread, processing of next frame will 
> be done and in the other, rendering of the previous frame. Here, 
> fgMainLoop() is split into two threads, all the processing before 
> calling fgRenderFrame() in one thread, i.e. subsystem updates, 
> input/output updates, tile manager updates,  etc., and fgRenderFrame() 
> in the other thread.
> 
> Is this the correct method of splitting processing and rendering of 
> frame data?
> 
> We are using the below to create a thread:
> hThread[1] = 
> CreateThread(NULL,0,(LPTHREAD_START_ROUTINE)fgRenderFrame1,NULL,0,&dwID[1]);
>       CloseHandle(hThread[1]);
> 
> Using the above gives us stack dump error.
> 
> Please give us a solution as to how to implement threading.
> Eagerly waiting for your reply.

Re: [Plib-users] Multithreading in FG

[Stuart M. <stu...@bl...>]

Hi,
   I can't see anything obviously wrong with that code, but here's the
solution I used.
 
I used the set of headers for threading from
 
http://www.codeproject.com/threads/thread_class.asp
 
These work on both linux and windows (and cygwin). I got them working
with no knowledge of threading
straight away and they provide a nice clean interface. They also have
mutex and semaphore classes
which are also very handy for threaded apps.
 
The code is small, easy to see what's going on and well documented. Even
if you don't use it it's
probably worth looking at to see if it helps with your problem.
 
   Good luck,
 
Stuart.
 
 
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Hemalatha
Sharma
Sent: Monday, August 28, 2006 1:29 PM
To: fli...@fl...;
fli...@li...;
fli...@fl...
Cc: pli...@li...;
pli...@li...
Subject: [Plib-users] Multithreading in FG
 
  Hi,
We are using Flightgear version 0.9.4, in which we are trying to
implement multi-threading. In one thread, processing of next frame will
be done and in the other, rendering of the previous frame. Here,
fgMainLoop() is split into two threads, all the processing before
calling fgRenderFrame() in one thread, i.e. subsystem updates,
input/output updates, tile manager updates,  etc., and fgRenderFrame()
in the other thread.

Is this the correct method of splitting processing and rendering of
frame data?

We are using the below to create a thread:
hThread[1] =
CreateThread(NULL,0,(LPTHREAD_START_ROUTINE)fgRenderFrame1,NULL,0,&dwID[
1]);
      CloseHandle(hThread[1]);

Using the above gives us stack dump error.

Please give us a solution as to how to implement threading.
Eagerly waiting for your reply.

Regards,
Hemalatha


 
<http://adworks.rediff.com/cgi-bin/AdWorks/sigclick.cgi/www.rediff.com/s
ignature-home.htm/1507191490@Middle5?PARTNER=3> 

[Plib-users] Multithreading in FG

[Hemalatha S. <hem...@re...>]

 =A0Hi,=0AWe are using Flightgear version 0.9.4, in which we are trying to =
implement multi-threading. In one thread, processing of next frame will be =
done and in the other, rendering of the previous frame. Here, fgMainLoop() =
is split into two threads, all the processing before calling fgRenderFrame(=
) in one thread, i.e. subsystem updates, input/output updates, tile manager=
 updates,  etc., and fgRenderFrame() in the other thread.=0A=0AIs this the =
correct method of splitting processing and rendering of frame data?=0A=0AWe=
 are using the below to create a thread:=0AhThread[1] =3D CreateThread(NULL=
,0,(LPTHREAD_START_ROUTINE)fgRenderFrame1,NULL,0,&dwID[1]);=0A	 CloseHandle=
(hThread[1]);=0A=0AUsing the above gives us stack dump error.=0A=0APlease g=
ive us a solution as to how to implement threading.=0AEagerly waiting for y=
our reply.=0A=0ARegards,=0AHemalatha=0A=0A

[Plib-users] plib examples configure problem

[Michael S. <mse...@ho...>]

hi i want to check out the plib examples, but ./configure doesn't work.  In 
fact the problem is the same one as was reported to this mailing list at the 
beginning of this year with this heading:

>>From: Paxton C. Sanders <pcsanders@ya...>
>>Bug: Examples configure script reliably fails  2006-01-14 20:07

Anyway heres the output i get when i type './configure'.  I am using 32 bit 
Fedora Core 2.

[root@localhost plib_examples-1.8.4]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
configure: error: cannot run /bin/sh ./config.sub
[root@localhost plib_examples-1.8.4]#

Re: [Plib-users] convert from geodetic data to screen coordinates

[Tinoshi K. <ti...@li...>]

Hi,

don't know if it helps, but this is a method for the class Mouse, class =
that I use to deal with ecerything concerned to the mouse, of course :-) =

Given the mouse position on the screen (x and y) it returns an =
sdgLineSegment3* ... I use it 'cause I'm developing a scenario creation =
program=20
for my flight simulator, and I want it to look like Sim City or stuff =
like that, so that I can put houses and trees and facilities on the
terrain map just clicking with the mouse... this is the sgdLineSegment3* =
that you will test against the terrain scenegraph to get the triangles =
that
collided 'under' your mouse arrow... Ok, weird explanation, sorry :-P =
but it performs the unproject stuff from 2D to 3D and of course you get =
a line
cause you are moving from 2D space to 3D space...
=20
sgdLineSegment3* Mouse::unproject(int x, int y)
{
GLint viewport[4];
GLdouble projmatrix[16],mvmatrix[16];
GLint realy;  /*  OpenGL y coordinate position  */
GLdouble wx, wy, wz;  /*  returned world x, y, z coords  */
GLdouble wxw, wyw, wzw;

/* Load the OpenGL matrices (biewport and projection are correct, =
modelview is Ones) */
glGetIntegerv (GL_VIEWPORT, viewport);
glGetDoublev (GL_PROJECTION_MATRIX, projmatrix);
glGetDoublev (GL_MODELVIEW_MATRIX, mvmatrix);

// Get the current context
ssgContext *curr_context =3D ssgGetCurrentContext();

/* Create a support sgMat4 for MODELVIEW */
sgMat4 modelview;
curr_context->getModelviewMatrix(modelview);

/* This matrix should be of doubles!!! */
sgdMat4 d_modelview;
makeSgMat4double(modelview,d_modelview);

/* Create a support matrix for PROJECTION */
sgMat4 projection;
curr_context->getProjectionMatrix(projection);

/* This matrix shoul be of doubles!!! */
sgdMat4 d_projection;
makeSgMat4double(projection,d_projection);

/*  note viewport[3] is height of window in pixels  */
realy =3D viewport[3] - (GLint) y - 1;

gluUnProject ((GLdouble) x, (GLdouble) realy, 0.0, (GLdouble *) =
d_modelview, (GLdouble *)d_projection, viewport, &wx, &wy, &wz);=20
gluUnProject ((GLdouble) x, (GLdouble) realy, 1.0, (GLdouble *) =
d_modelview, (GLdouble *)d_projection, viewport, &wxw, &wyw, &wzw);=20

// Create the sgVec3* line (used for SSG_ISECT!!!)
sgdLineSegment3 *lineS =3D =
(sgdLineSegment3*)malloc(sizeof(sgdLineSegment3));
sgdSetVec3(lineS->a,wxw, wyw, wzw);
sgdSetVec3(lineS->b,wx, wy, wz);

curr_context->setNearFar(CAMERA_NEAR,CAMERA_FAR);

return lineS;
}

Re: [Plib-users] (no subject)

[steve <sjb...@ai...>]

Hemalatha Sharma wrote:
>  
> Hi,
> I am mailing again.
> There was no reply for my query.

All four(!) copies of your email arrived simultaneously - you
need to exhibit some more patience.

> I need to convert from geodetic data to screen coordinates.
> How can i do it?
> 
> There is a function in SimGear(SgGeodToCart) which converts geodetic 
> lat,long to cartesian form.
> But How do i convert from catesian to screen cartesian form.

Geodetic to cartesian is definitely not a PLIB thing - so you're
right to seek help in SimGear.

Cartesian to screen coordinates is probably best handled by the
OpenGL function 'gluProject'...so this isn't really a PLIB question
either.  However:

GLint gluProject ( GLdouble objX, GLdouble objY, GLdouble objZ,
                    const GLdouble *model,
                    const GLdouble *proj,
                    const GLint *view,
                    GLdouble* winX, GLdouble* winY, GLdouble* winZ);

Where:

   (objX, objY, objZ) is the cartesian coordinate you are
                      concerned about.
   model, proj        are the OpenGL modelview and projection matrix.
                      You can either get these by doing a glGetMatrix()
                      or inside SSG you can use
                      ssgContext::getProjectionMatrix()
                      and ssgContext::getModelviewMatrix().
   view               is an array containing the viewport parameters.
                      You get this with glGetFloatv(GL_VIEWPORT,...).
   (winX, winY, winZ) are pointers to where you'd like the return
                      results placed.

Re: [Plib-users] convert from geodetic data to screen coordinates

[Fay J. F Dr C. U. AFSEO/SK <joh...@eg...>]

Hemalatha,

	You will need a translation and a rotation.  The details will depend
on the geodetic coordinate system and the screen coordinate system that you
are using.

John F. Fay
Technical Fellow, Jacobs/Sverdrup TEAS Group
850-883-1294
joh...@eg...
 

[Plib-users] convert from geodetic data to screen coordinates

[Hemalatha S. <hem...@re...>]

 =A0=0AHi,=0AI am mailing again.=0AThere was no reply for my query.=0APlz..=
.........do reply =0AI need to convert from geodetic data to screen coordin=
ates.=0AHow can i do it?=0A=0AThere is a function in SimGear(SgGeodToCart) =
which converts geodetic lat,long to cartesian form.=0ABut How do i convert =
from catesian to screen cartesian form.=0A=0A=0AThanks & Regards=0AHemalath=
a =0A=0A=0A

[Plib-users] (no subject)

[Hemalatha S. <hem...@re...>]

 =A0=0AHi,=0AI am mailing again.=0AThere was no reply for my query.=0APlz..=
.........do reply =0AI need to convert from geodetic data to screen coordin=
ates.=0AHow can i do it?=0A=0AThere is a function in SimGear(SgGeodToCart) =
which converts geodetic lat,long to cartesian form.=0ABut How do i convert =
from catesian to screen cartesian form.=0A=0A=0AThanks & Regards=0AHemalath=
a =0A=0A=0A

[Plib-users] (no subject)

[Hemalatha S. <hem...@re...>]

 =A0=0AHi,=0AI am mailing again.=0AThere was no reply for my query.=0APlz..=
.........do reply =0AI need to convert from geodetic data to screen coordin=
ates.=0AHow can i do it?=0A=0AThere is a function in SimGear(SgGeodToCart) =
which converts geodetic lat,long to cartesian form.=0ABut How do i convert =
from catesian to screen cartesian form.=0A=0A=0AThanks & Regards=0AHemalath=
a =0A=0A=0A

[Plib-users] (no subject)

[Hemalatha S. <hem...@re...>]

 =A0=0AHi,=0AI am mailing again.=0AThere was no reply for my query.=0APlz..=
.........do reply =0AI need to convert from geodetic data to screen coordin=
ates.=0AHow can i do it?=0A=0AThere is a function in SimGear(SgGeodToCart) =
which converts geodetic lat,long to cartesian form.=0ABut How do i convert =
from catesian to screen cartesian form.=0A=0A=0AThanks & Regards=0AHemalath=
a =0A=0A=0A

Re: [Plib-users] (newbie) Compile errors when installing PLIB examples + documentation.

[<eke...@ho...>]

I sent e-mail to Darrell Walisser, the "Mac guru" of PLIB, and waited for 
quite a while. Then, the e-mail bounced back to me with the notice that it 
couldn't be sent...... :(

_________________________________________________________________
Nyt löydät etsimäsi tiedot nopeasti niin koneeltasi kuin netistä. 
http://toolbar.msn.fi

Re: [Plib-users] plib-users Digest, Vol 1, Issue 772

[Fay J. F Dr C. U. AFSEO/SK <joh...@eg...>]

Just for the record, the "extern "C"" did not cause the error messages =
that
you listed in your first post.

John F. Fay
Technical Fellow, Jacobs/Sverdrup TEAS Group
850-883-1294
joh...@eg...
=20
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Otto =
Halm=E9n
Sent: Saturday, June 03, 2006 2:46 PM
To: pli...@li...
Subject: Re: [Plib-users] plib-users Digest, Vol 1, Issue 772

>From: Jonathan Pilborough <j_p...@ya...>
>Reply-To: Jonathan Pilborough <j_p...@ya...>,PLIB Users=20
><pli...@li...>
>To: pli...@li...
>Subject: Re: [Plib-users] plib-users Digest, Vol 1, Issue 772
>Date: Sat, 3 Jun 2006 19:16:40 +0000 (GMT)
>
>Get rid of it - and the other closing bracket. I'm no expert, but it's =

>worth a try.
>Regards,
>JP

Hi,
Installing PLIB examples after building PLIB after getting rid of =
'extern
"C"' on line 273 in "ul.h" results in an error. Calling configure for =
PLIB
examples:

+++++++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ ./configure =
checking
for a BSD-compatible install... /usr/bin/install -c checking whether =
build
environment is sane... yes checking for gawk... no checking for mawk... =
no
checking for nawk... no checking for awk... awk checking whether make =
sets
$(MAKE)... yes checking for gcc... gcc checking for C compiler default
output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no checking for suffix of
executables...
checking for suffix of object files... o checking whether we are using =
the
GNU C compiler... yes checking whether gcc accepts -g... yes checking =
for
gcc option to accept ANSI C... none needed checking for style of =
include
used by make... GNU checking dependency style of gcc... gcc3 checking =
how to
run the C preprocessor... gcc -E checking for g++... g++ checking =
whether we
are using the GNU C++ compiler... yes checking whether g++ accepts =
-g... yes
checking dependency style of g++... gcc3 checking how to run the C++
preprocessor... g++ -E checking for a BSD-compatible install...
/usr/bin/install -c checking build system type... =
powerpc-apple-darwin8.6.0
checking host system type... powerpc-apple-darwin8.6.0 checking for =
ulInit
in -lplibul... no
configure: error: there seems to be a problem with the PLIB libraries
Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++++++

If 'extern"C"' is necessary for the configure script, but preventing =
PLIB
applications from building, then what should I do?

-Otto

_________________________________________________________________
Uutisista turhaan tietoon. Mit=E4 ikin=E4 etsitkin, MSN Search =
l=F6yt=E4=E4 hakemasi.=20
http://search.msn.fi



_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users

Re: [Plib-users] (newbie) Compile errors when installing PLIB exa mples + documentation.

[Fay J. F Dr C. U. AFSEO/SK <joh...@eg...>]

Otto,

	Please pardon my delay in answering you.

	From your description below, it looks a lot like you are trying to
compile the "ul" library with a C program instead of with a C++ =
program.
The C language does not distinguish between "inline void
ulEndianSwap(unsigned int *x)" and "inline void ulEndianSwap(unsigned =
short
*x)" while C++ does.  That will cause the compiler errors you are =
getting.

	Why the compiler is doing this with the example files is beyond me.

John F. Fay
Technical Fellow, Jacobs/Sverdrup TEAS Group
850-883-1294
joh...@eg...
=20
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Otto =
Halm=E9n
Sent: Friday, June 02, 2006 7:44 AM
To: pli...@li...
Subject: [Plib-users] (newbie) Compile errors when installing PLIB =
examples
+ documentation.

It seems that I have managed to install PLIB successfully, because =
although
the terminal displayed strange information, all the files had been =
installed
in their correct locations.

But now, when installing the PLIB examples + documentation package, I =
get
problems.

Calling ./configure

+++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ ./configure =
checking
for a BSD-compatible install... /usr/bin/install -c checking whether =
build
environment is sane... yes checking for gawk... no checking for mawk... =
no
checking for nawk... no checking for awk... awk checking whether make =
sets
$(MAKE)... yes checking for gcc... gcc checking for C compiler default
output file name... a.out checking whether the C compiler works... yes
checking whether we are cross compiling... no checking for suffix of
executables...
checking for suffix of object files... o checking whether we are using =
the
GNU C compiler... yes checking whether gcc accepts -g... yes checking =
for
gcc option to accept ANSI C... none needed checking for style of =
include
used by make... GNU checking dependency style of gcc... gcc3 checking =
how to
run the C preprocessor... gcc -E checking for g++... g++ checking =
whether we
are using the GNU C++ compiler... yes checking whether g++ accepts =
-g... yes
checking dependency style of g++... gcc3 checking how to run the C++
preprocessor... g++ -E checking for a BSD-compatible install...
/usr/bin/install -c checking build system type... =
powerpc-apple-darwin8.6.0
checking host system type... powerpc-apple-darwin8.6.0 checking for =
ulInit
in -lplibul... yes checking for egrep... grep -E checking for ANSI C =
header
files... yes checking for sys/types.h... yes checking for sys/stat.h... =
yes
checking for stdlib.h... yes checking for string.h... yes checking for
memory.h... yes checking for strings.h... yes checking for =
inttypes.h... yes
checking for stdint.h... yes checking for unistd.h... yes checking =
windows.h
usability... no checking windows.h presence... no checking for =
windows.h...
no checking OpenGL/gl.h usability... yes checking OpenGL/gl.h =
presence...
yes checking for OpenGL/gl.h... yes checking OpenGL/glu.h usability... =
yes
checking OpenGL/glu.h presence... yes checking for OpenGL/glu.h... yes
checking GLUT/glut.h usability... yes checking GLUT/glut.h presence... =
yes
checking for GLUT/glut.h... yes checking plib/ul.h usability... no =
checking
plib/ul.h presence... yes
configure: WARNING: plib/ul.h: present but cannot be compiled
configure: WARNING: plib/ul.h:     check for missing prerequisite =
headers?
configure: WARNING: plib/ul.h: see the Autoconf documentation
configure: WARNING: plib/ul.h:     section "Present But Cannot Be =
Compiled"
configure: WARNING: plib/ul.h: proceeding with the preprocessor's =
result
configure: WARNING: plib/ul.h: in the future, the compiler will take
precedence
configure: WARNING:     ## ------------------------------------------ =
##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  =
##
configure: WARNING:     ## ------------------------------------------ =
##
checking for plib/ul.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/js/Makefile
config.status: creating src/pw/Makefile
config.status: creating src/pui/Makefile
config.status: creating src/sg/Makefile
config.status: creating src/sl/Makefile
config.status: creating src/ssg/Makefile
config.status: creating src/ssg/tux/Makefile
config.status: creating src/ssg/majik/Makefile
config.status: creating src/ssg/load_save/Makefile
config.status: creating src/ssg/state_test/Makefile
config.status: creating src/ssg/tween_test/Makefile
config.status: creating src/ssg/viewer/Makefile
config.status: creating src/ssg/water/Makefile
config.status: creating src/ssg/sky/Makefile
config.status: creating src/ssg/dynamics/Makefile
config.status: creating src/ssg/shrubs/Makefile
config.status: creating src/fnt/Makefile
config.status: creating src/net/Makefile
config.status: creating src/net/client_server/Makefile
config.status: creating src/net/http_get/Makefile
config.status: creating src/net/net_echo/Makefile
config.status: creating src/psl/Makefile
config.status: creating src/util/Makefile
config.status: executing depfiles commands PLIB configuration =
information:

  Building FNT examples:         yes
  Building JS examples:          yes
  Building PW examples:          yes
  Building NET examples:         yes
  Building PUI examples:         yes
  Building SG examples:          yes
  Building PSL examples:         yes
  Building SL examples:          yes
  Building SSG/ssgAux examples:  yes
  Building UTIL examples:        yes

  Need GLUT:                     yes (found GLUT)

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++

Something seemed to go wrong in the middle of the procedure, but it =
still
continued to the end. Peculiar. Anyway, now calling make:

+++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ make Making all in =
src
Making all in js source=3D'js_demo.cxx' object=3D'js_demo.o' =
libtool=3Dno \
depfile=3D'.deps/js_demo.Po' tmpdepfile=3D'.deps/js_demo.TPo' \
depmode=3Dgcc3 /bin/sh ../../depcomp \
g++ -DPACKAGE_NAME=3D\"\" -DPACKAGE_TARNAME=3D\"\" =
-DPACKAGE_VERSION=3D\"\"=20
-DPACKAGE_STRING=3D\"\" -DPACKAGE_BUGREPORT=3D\"\" =
-DPACKAGE=3D\"plib_examples\"=20
-DVERSION=3D\"1.8.4\" -DSTDC_HEADERS=3D1 -DHAVE_SYS_TYPES_H=3D1
-DHAVE_SYS_STAT_H=3D1 -DHAVE_STDLIB_H=3D1 -DHAVE_STRING_H=3D1 =
-DHAVE_MEMORY_H=3D1
-DHAVE_STRINGS_H=3D1 -DHAVE_INTTYPES_H=3D1 -DHAVE_STDINT_H=3D1 =
-DHAVE_UNISTD_H=3D1=20
-DHAVE_OPENGL_GL_H=3D1 -DHAVE_OPENGL_GLU_H=3D1 -DGLUT_IS_PRESENT=3D1  =
-I. -I.    =20
-g -O2 -Wall -c -o js_demo.o `test -f 'js_demo.cxx' || echo =
'./'`js_demo.cxx
/usr/include/plib/ul.h: In function `void ulEndianSwap(short unsigned
int*)':
/usr/include/plib/ul.h:342: error: declaration of C function 'void
ulEndianSwap(short unsigned int*)' conflicts with
/usr/include/plib/ul.h:333: error: previous declaration 'void
ulEndianSwap(unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:349: error: declaration of C function 'void
ulEndianSwap(float*)' conflicts with
/usr/include/plib/ul.h:342: error: previous declaration 'void
ulEndianSwap(short unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:349: 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:350: error: declaration of C function 'void
ulEndianSwap(int*)' conflicts with
/usr/include/plib/ul.h:349: error: previous declaration 'void
ulEndianSwap(float*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:350: error: invalid conversion from 'unsigned =
int*'=20
to 'int*'
/usr/include/plib/ul.h:350: error:   initializing argument 1 of 'void=20
ulEndianSwap(int*)'
/usr/include/plib/ul.h: In function `void ulEndianSwap(short int*)':
/usr/include/plib/ul.h:351: error: declaration of C function 'void
ulEndianSwap(short int*)' conflicts with
/usr/include/plib/ul.h:350: error: previous declaration 'void
ulEndianSwap(int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:351: error: invalid conversion from 'short =
unsigned
int*' to 'short int*'
/usr/include/plib/ul.h:351: error:   initializing argument 1 of 'void=20
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `short unsigned int
ulEndianLittle16(short unsigned int)':
/usr/include/plib/ul.h:358: error: invalid conversion from 'short =
unsigned
int*' to 'short int*'
/usr/include/plib/ul.h:358: error:   initializing argument 1 of 'void=20
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `unsigned int =
ulEndianLittle32(unsigned
int)':
/usr/include/plib/ul.h:367: 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:376: error: cannot convert 'float*' to 'short =
int*'=20
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianLittleArray16(short
unsigned int*, int)':
/usr/include/plib/ul.h:386: error: invalid conversion from 'short =
unsigned
int*' to 'short int*'
/usr/include/plib/ul.h:386: error:   initializing argument 1 of 'void=20
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void =
ulEndianLittleArray32(unsigned
int*, int)':
/usr/include/plib/ul.h:396: 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:406: error: cannot convert 'float*' to 'short =
int*'=20
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArray16(short =
unsigned
int*, int)':
/usr/include/plib/ul.h:416: error: invalid conversion from 'short =
unsigned
int*' to 'short int*'
/usr/include/plib/ul.h:416: error:   initializing argument 1 of 'void=20
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArray32(unsigned =
int*,
int)':
/usr/include/plib/ul.h:426: 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:436: error: cannot convert 'float*' to 'short =
int*'=20
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `short unsigned int =
ulEndianBig16(short
unsigned int)':
/usr/include/plib/ul.h:445: error: invalid conversion from 'short =
unsigned
int*' to 'short int*'
/usr/include/plib/ul.h:445: error:   initializing argument 1 of 'void=20
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `unsigned int =
ulEndianBig32(unsigned
int)':
/usr/include/plib/ul.h:454: 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:463: error: cannot convert 'float*' to 'short =
int*'=20
for argument '1' to 'void ulEndianSwap(short int*)'
make[2]: *** [js_demo.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++

I don't know if I did something wrong or if it's the source, but it =
looks
like there are some errors in the source code. I don't know... As =
always, my
platform is MacMini G4 SD with MacOS X 10.4.6.

So, will I have to edit the source files by hand (again!) or is there =
an
easier way?

_________________________________________________________________
Uutisista turhaan tietoon. Mit=E4 ikin=E4 etsitkin, MSN Search =
l=F6yt=E4=E4 hakemasi.=20
http://search.msn.fi



_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users

Re: [Plib-users] (newbie) Compile errors when installing PLIB examples + documentation.

[<coz...@gm...>]

> There is a 'extern "C"' indeed, in "ul.h", line 273. If that's what's
> causing the problem, what should I do to it?


The thing is that the only extern "C" in the ul.h, however, it seems to
affect only the ulInit() function.

The line is just

extern "C" void ulInit();

There is a readme.mac file. In it says you should try emailing Darrell
Walisser using the address dwaliss1 <at> purdue.edu .

If he can help you fix this problem, please post the solution in the mailing
list.

-Coz

Re: [Plib-users] plib-users Digest, Vol 1, Issue 772

[<eke...@ho...>]

>From: Jonathan Pilborough <j_p...@ya...>
>Reply-To: Jonathan Pilborough <j_p...@ya...>,PLIB Users 
><pli...@li...>
>To: pli...@li...
>Subject: Re: [Plib-users] plib-users Digest, Vol 1, Issue 772
>Date: Sat, 3 Jun 2006 19:16:40 +0000 (GMT)
>
>Get rid of it - and the other closing bracket. I'm no expert, but it's 
>worth a try.
>Regards,
>JP

Hi,
Installing PLIB examples after building PLIB after getting rid of 'extern 
"C"' on line 273 in "ul.h" results in an error. Calling configure for PLIB 
examples:

+++++++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... powerpc-apple-darwin8.6.0
checking host system type... powerpc-apple-darwin8.6.0
checking for ulInit in -lplibul... no
configure: error: there seems to be a problem with the PLIB libraries
Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++++++

If 'extern"C"' is necessary for the configure script, but preventing PLIB 
applications from building, then what should I do?

-Otto

_________________________________________________________________
Uutisista turhaan tietoon. Mitä ikinä etsitkin, MSN Search löytää hakemasi. 
http://search.msn.fi

Re: [Plib-users] plib-users Digest, Vol 1, Issue 772

[Jonathan P. <j_p...@ya...>]

Get rid of it - and the other closing bracket. I'm no expert, but it's worth a try.
Regards,
JP

From: Otto Halm?n <eke...@ho...>
Subject: Re: [Plib-users] (newbie) Compile errors when installing PLIB
    examples + documentation.
To: pli...@li...
Message-ID: <BAY...@ph...l>
Content-Type: text/plain; charset=iso-8859-1; format=flowed

There is a 'extern "C"' indeed, in "ul.h", line 273. If that's what's 
causing the problem, what should I do to it?





------------------------------



------------------------------

_______________________________________________
plib-users mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-users


End of plib-users Digest, Vol 1, Issue 772
******************************************

Re: [Plib-users] (newbie) Compile errors when installing PLIB examples + documentation.

[<eke...@ho...>]

There is a 'extern "C"' indeed, in "ul.h", line 273. If that's what's 
causing the problem, what should I do to it?

_________________________________________________________________
Nyt löydät etsimäsi tiedot nopeasti niin koneeltasi kuin netistä. 
http://toolbar.msn.fi

Re: [Plib-users] (newbie) Compile errors when installing PLIB examples + documentation.

[<coz...@gm...>]

Hello,

I'm not sure how much I can help you, I don't own a mac... However, the
error seems that those functions are being linked as C functions instead of
C++ functions, which breaks function overloading.

Probably there is something being affected by an extern "C" somewhere, but I
couldn't find where...

And the thing seems to be that there aren't many people who would test plib
on the MacOSX so it can be fixed. The problem *could* be fixed in the
development tree.

-Coz

[Plib-users] (newbie) Compile errors when installing PLIB examples + documentation.

[<eke...@ho...>]

It seems that I have managed to install PLIB successfully, because although 
the terminal displayed strange information, all the files had been installed 
in their correct locations.

But now, when installing the PLIB examples + documentation package, I get 
problems.

Calling ./configure

+++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... powerpc-apple-darwin8.6.0
checking host system type... powerpc-apple-darwin8.6.0
checking for ulInit in -lplibul... yes
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking OpenGL/gl.h usability... yes
checking OpenGL/gl.h presence... yes
checking for OpenGL/gl.h... yes
checking OpenGL/glu.h usability... yes
checking OpenGL/glu.h presence... yes
checking for OpenGL/glu.h... yes
checking GLUT/glut.h usability... yes
checking GLUT/glut.h presence... yes
checking for GLUT/glut.h... yes
checking plib/ul.h usability... no
checking plib/ul.h presence... yes
configure: WARNING: plib/ul.h: present but cannot be compiled
configure: WARNING: plib/ul.h:     check for missing prerequisite headers?
configure: WARNING: plib/ul.h: see the Autoconf documentation
configure: WARNING: plib/ul.h:     section "Present But Cannot Be Compiled"
configure: WARNING: plib/ul.h: proceeding with the preprocessor's result
configure: WARNING: plib/ul.h: in the future, the compiler will take 
precedence
configure: WARNING:     ## ------------------------------------------ ##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  ##
configure: WARNING:     ## ------------------------------------------ ##
checking for plib/ul.h... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/js/Makefile
config.status: creating src/pw/Makefile
config.status: creating src/pui/Makefile
config.status: creating src/sg/Makefile
config.status: creating src/sl/Makefile
config.status: creating src/ssg/Makefile
config.status: creating src/ssg/tux/Makefile
config.status: creating src/ssg/majik/Makefile
config.status: creating src/ssg/load_save/Makefile
config.status: creating src/ssg/state_test/Makefile
config.status: creating src/ssg/tween_test/Makefile
config.status: creating src/ssg/viewer/Makefile
config.status: creating src/ssg/water/Makefile
config.status: creating src/ssg/sky/Makefile
config.status: creating src/ssg/dynamics/Makefile
config.status: creating src/ssg/shrubs/Makefile
config.status: creating src/fnt/Makefile
config.status: creating src/net/Makefile
config.status: creating src/net/client_server/Makefile
config.status: creating src/net/http_get/Makefile
config.status: creating src/net/net_echo/Makefile
config.status: creating src/psl/Makefile
config.status: creating src/util/Makefile
config.status: executing depfiles commands
PLIB configuration information:

  Building FNT examples:         yes
  Building JS examples:          yes
  Building PW examples:          yes
  Building NET examples:         yes
  Building PUI examples:         yes
  Building SG examples:          yes
  Building PSL examples:         yes
  Building SL examples:          yes
  Building SSG/ssgAux examples:  yes
  Building UTIL examples:        yes

  Need GLUT:                     yes (found GLUT)

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++

Something seemed to go wrong in the middle of the procedure, but it still 
continued to the end. Peculiar. Anyway, now calling make:

+++++++++++++++++++++++++++++++++++++++++++

Macintosh:/developer/plib_examples-1.8.4 ottohalmen$ make
Making all in src
Making all in js
source='js_demo.cxx' object='js_demo.o' libtool=no \
depfile='.deps/js_demo.Po' tmpdepfile='.deps/js_demo.TPo' \
depmode=gcc3 /bin/sh ../../depcomp \
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib_examples\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_OPENGL_GL_H=1 -DHAVE_OPENGL_GLU_H=1 -DGLUT_IS_PRESENT=1  -I. -I.     
-g -O2 -Wall -c -o js_demo.o `test -f 'js_demo.cxx' || echo './'`js_demo.cxx
/usr/include/plib/ul.h: In function `void ulEndianSwap(short unsigned 
int*)':
/usr/include/plib/ul.h:342: error: declaration of C function 'void 
ulEndianSwap(short unsigned int*)' conflicts with
/usr/include/plib/ul.h:333: error: previous declaration 'void 
ulEndianSwap(unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:349: error: declaration of C function 'void 
ulEndianSwap(float*)' conflicts with
/usr/include/plib/ul.h:342: error: previous declaration 'void 
ulEndianSwap(short unsigned int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:349: 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:350: error: declaration of C function 'void 
ulEndianSwap(int*)' conflicts with
/usr/include/plib/ul.h:349: error: previous declaration 'void 
ulEndianSwap(float*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:350: error: invalid conversion from 'unsigned int*' 
to 'int*'
/usr/include/plib/ul.h:350: error:   initializing argument 1 of 'void 
ulEndianSwap(int*)'
/usr/include/plib/ul.h: In function `void ulEndianSwap(short int*)':
/usr/include/plib/ul.h:351: error: declaration of C function 'void 
ulEndianSwap(short int*)' conflicts with
/usr/include/plib/ul.h:350: error: previous declaration 'void 
ulEndianSwap(int*)' here
/usr/include/plib/ul.h: In function `void ulEndianSwap(float*)':
/usr/include/plib/ul.h:351: error: invalid conversion from 'short unsigned 
int*' to 'short int*'
/usr/include/plib/ul.h:351: error:   initializing argument 1 of 'void 
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `short unsigned int 
ulEndianLittle16(short unsigned int)':
/usr/include/plib/ul.h:358: error: invalid conversion from 'short unsigned 
int*' to 'short int*'
/usr/include/plib/ul.h:358: error:   initializing argument 1 of 'void 
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `unsigned int ulEndianLittle32(unsigned 
int)':
/usr/include/plib/ul.h:367: 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:376: error: cannot convert 'float*' to 'short int*' 
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianLittleArray16(short 
unsigned int*, int)':
/usr/include/plib/ul.h:386: error: invalid conversion from 'short unsigned 
int*' to 'short int*'
/usr/include/plib/ul.h:386: error:   initializing argument 1 of 'void 
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianLittleArray32(unsigned 
int*, int)':
/usr/include/plib/ul.h:396: 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:406: error: cannot convert 'float*' to 'short int*' 
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArray16(short unsigned 
int*, int)':
/usr/include/plib/ul.h:416: error: invalid conversion from 'short unsigned 
int*' to 'short int*'
/usr/include/plib/ul.h:416: error:   initializing argument 1 of 'void 
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `void ulEndianBigArray32(unsigned int*, 
int)':
/usr/include/plib/ul.h:426: 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:436: error: cannot convert 'float*' to 'short int*' 
for argument '1' to 'void ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `short unsigned int ulEndianBig16(short 
unsigned int)':
/usr/include/plib/ul.h:445: error: invalid conversion from 'short unsigned 
int*' to 'short int*'
/usr/include/plib/ul.h:445: error:   initializing argument 1 of 'void 
ulEndianSwap(short int*)'
/usr/include/plib/ul.h: In function `unsigned int ulEndianBig32(unsigned 
int)':
/usr/include/plib/ul.h:454: 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:463: error: cannot convert 'float*' to 'short int*' 
for argument '1' to 'void ulEndianSwap(short int*)'
make[2]: *** [js_demo.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
Macintosh:/developer/plib_examples-1.8.4 ottohalmen$

+++++++++++++++++++++++++++++++++++++++++++

I don't know if I did something wrong or if it's the source, but it looks 
like there are some errors in the source code. I don't know... As always, my 
platform is MacMini G4 SD with MacOS X 10.4.6.

So, will I have to edit the source files by hand (again!) or is there an 
easier way?

_________________________________________________________________
Uutisista turhaan tietoon. Mitä ikinä etsitkin, MSN Search löytää hakemasi. 
http://search.msn.fi

Re: [Plib-users] (newbie) Problems with installing PLIB on a Macintosh.

[<coz...@gm...>]

Hello,

I am a rookie programmer, and new to both UNIX and PLIB. I've seen several
> free, cross-platform, hardware accelerated game development libraries, and
> PLIB seems to be the best, as it is written in C++ and doesn't require
> dozens of other libraries to be installed already.
>
> When I tried, following the instructions on the page
> http://plib.sourceforge.net/download.html, to install the API on my
> MacMini
> G4 SuperDrive with MacOS X 10.4 and the bundled XCode Tools, everything
> seemed fine at first. I ran "./configure", getting this result:

[...]


Well, I checked the source(I'm not really using a mac) and it seems that
both the function implementation and declaration for the function
os_specific_s::elementEnumerator are using the static keyword but only the
declaration should have it.

In other words, in the file src/js/jsMacOSX.cxx at the line 278 the static
keyword shouldn't be there. Just erase it. The people with commit access
could delete the keyword from there and commit the change.

-Coz

[Plib-users] (newbie) Problems with installing PLIB on a Macintosh.

[<eke...@ho...>]

Hello.

I am a rookie programmer, and new to both UNIX and PLIB. I've seen several 
free, cross-platform, hardware accelerated game development libraries, and 
PLIB seems to be the best, as it is written in C++ and doesn't require 
dozens of other libraries to be installed already.

When I tried, following the instructions on the page 
http://plib.sourceforge.net/download.html, to install the API on my MacMini 
G4 SuperDrive with MacOS X 10.4 and the bundled XCode Tools, everything 
seemed fine at first. I ran "./configure", getting this result:

------------------------------------------------------------------

Macintosh:/developer/plib-1.8.4 ottohalmen$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
includedir changed to ${prefix}/include/plib libdir is ${exec_prefix}/lib
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking build system type... powerpc-apple-darwin8.6.0
checking host system type... powerpc-apple-darwin8.6.0
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking OpenGL/gl.h usability... yes
checking OpenGL/gl.h presence... yes
checking for OpenGL/gl.h... yes
checking for pthread_exit in -lc_r... no
checking for socklen_t... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/js/Makefile
config.status: creating src/util/Makefile
config.status: creating src/sg/Makefile
config.status: creating src/sl/Makefile
config.status: creating src/psl/Makefile
config.status: creating src/ssg/Makefile
config.status: creating src/ssgAux/Makefile
config.status: creating src/fnt/Makefile
config.status: creating src/pui/Makefile
config.status: creating src/puAux/Makefile
config.status: creating src/pw/Makefile
config.status: creating src/net/Makefile
config.status: executing depfiles commands
PLIB configuration information:

  Building FNT library:     yes
  Building JS library:      yes
  Building NET library:     yes
  Building PUI library:     yes
  Building puAux library:   yes
  Building SG library:      yes
  Building PSL library:     yes
  Building SL library:      yes
  Building SSG library:     yes
  Building ssgAux library:  yes
  Building PW library:      yes
  Building UTIL library:    yes

------------------------------------------------------------------

But when I tried running "sudo make install" ("sudo" to become the root, as 
told in "http://plib.sourceforge.net/download.html"), I got the following:

------------------------------------------------------------------

Macintosh:/developer/plib-1.8.4 ottohalmen$ sudo make install
Password:
Sorry, try again.
Password:
Making install in src
Making install in util
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ul.o -MD -MP -MF ".deps/ul.Tpo" -c -o ul.o 
ul.cxx; \
then mv -f ".deps/ul.Tpo" ".deps/ul.Po"; else rm -f ".deps/ul.Tpo"; exit 1; 
fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ulClock.o -MD -MP -MF ".deps/ulClock.Tpo" -c -o 
ulClock.o ulClock.cxx; \
then mv -f ".deps/ulClock.Tpo" ".deps/ulClock.Po"; else rm -f 
".deps/ulClock.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ulError.o -MD -MP -MF ".deps/ulError.Tpo" -c -o 
ulError.o ulError.cxx; \
then mv -f ".deps/ulError.Tpo" ".deps/ulError.Po"; else rm -f 
".deps/ulError.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ulLinkedList.o -MD -MP -MF 
".deps/ulLinkedList.Tpo" -c -o ulLinkedList.o ulLinkedList.cxx; \
then mv -f ".deps/ulLinkedList.Tpo" ".deps/ulLinkedList.Po"; else rm -f 
".deps/ulLinkedList.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ulList.o -MD -MP -MF ".deps/ulList.Tpo" -c -o 
ulList.o ulList.cxx; \
then mv -f ".deps/ulList.Tpo" ".deps/ulList.Po"; else rm -f 
".deps/ulList.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I.     -g -O2 -Wall -MT ulRTTI.o -MD -MP -MF ".deps/ulRTTI.Tpo" -c -o 
ulRTTI.o ulRTTI.cxx; \
then mv -f ".deps/ulRTTI.Tpo" ".deps/ulRTTI.Po"; else rm -f 
".deps/ulRTTI.Tpo"; exit 1; fi
rm -f libplibul.a
ar cru libplibul.a ul.o ulClock.o ulError.o ulLinkedList.o ulList.o ulRTTI.o
ranlib libplibul.a
test -z "/usr/lib" || /developer/plib-1.8.4/install-sh -d "/usr/lib"
/usr/bin/install -c -m 644 'libplibul.a' '/usr/lib/libplibul.a'
ranlib '/usr/lib/libplibul.a'
test -z "/usr/include/plib" || /developer/plib-1.8.4/install-sh -d 
"/usr/include/plib"
/usr/bin/install -c -m 644 'ul.h' '/usr/include/plib/ul.h'
/usr/bin/install -c -m 644 'ulRTTI.h' '/usr/include/plib/ulRTTI.h'
Making install in js
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I. -I../../src/util    -g -O2 -Wall -MT js.o -MD -MP -MF ".deps/js.Tpo" 
-c -o js.o js.cxx; \
then mv -f ".deps/js.Tpo" ".deps/js.Po"; else rm -f ".deps/js.Tpo"; exit 1; 
fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I. -I../../src/util    -g -O2 -Wall -MT jsLinux.o -MD -MP -MF 
".deps/jsLinux.Tpo" -c -o jsLinux.o jsLinux.cxx; \
then mv -f ".deps/jsLinux.Tpo" ".deps/jsLinux.Po"; else rm -f 
".deps/jsLinux.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I. -I../../src/util    -g -O2 -Wall -MT jsLinuxOld.o -MD -MP -MF 
".deps/jsLinuxOld.Tpo" -c -o jsLinuxOld.o jsLinuxOld.cxx; \
then mv -f ".deps/jsLinuxOld.Tpo" ".deps/jsLinuxOld.Po"; else rm -f 
".deps/jsLinuxOld.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I. -I../../src/util    -g -O2 -Wall -MT jsMacOS.o -MD -MP -MF 
".deps/jsMacOS.Tpo" -c -o jsMacOS.o jsMacOS.cxx; \
then mv -f ".deps/jsMacOS.Tpo" ".deps/jsMacOS.Po"; else rm -f 
".deps/jsMacOS.Tpo"; exit 1; fi
if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"plib\" 
-DVERSION=\"1.8.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1  
-I. -I. -I../../src/util    -g -O2 -Wall -MT jsMacOSX.o -MD -MP -MF 
".deps/jsMacOSX.Tpo" -c -o jsMacOSX.o jsMacOSX.cxx; \
then mv -f ".deps/jsMacOSX.Tpo" ".deps/jsMacOSX.Po"; else rm -f 
".deps/jsMacOSX.Tpo"; exit 1; fi
jsMacOSX.cxx:278: error: cannot declare member function 'static void 
os_specific_s::elementEnumerator(const void*, void*)' to have static linkage
make[2]: *** [jsMacOSX.o] Error 1
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1

------------------------------------------------------------------

As I said, I am a newbie, so it might be that I have done something wrong 
(other than what lines 2-3 say!), but the debug text following my call to 
"sudo make install" doesn't tell me much. I already wrote to Steve J. Baker 
(before finding out about this place), but he merely told me to write here.
Hopefully, someone more familiar with the system could help me with this 
(please!).

-Otto

_________________________________________________________________
Uutisista turhaan tietoon. Mitä ikinä etsitkin, MSN Search löytää hakemasi. 
http://search.msn.fi