Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

You need to make os_specific_s::elementEnumerator not static as you
did but that's the only change I needed to make using the latest plib
cvs.
I'll add more detail in the ReadMe.

I believe there are some more changes you need to make in the official
plib 1.8.4 release but I don't remember them.
You can try searching the plib mailing list archives as that's where I
found the fix.

On 11/16/05, Adam Dershowitz <[EMAIL PROTECTED]> wrote:
>
>
> --Adam
>
>
>
> On Nov 14, 2005, at 7:23 AM, Arthur Wiebe wrote:
>
> >> Please do commit them, I've had hand-rolled projects for all three
> >> for some
> >> time, but they're out of sync. If I find any issues, I'll let you
> >> know.
> >>
> >> James
> >>
> >
> > OK, they are available now. I quickly wrote ReadMe's for them.
> >
> > https://sourceforge.net/cvs/?group_id=126825
> >
> > To checkout:
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P flightgear
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P SimGear
> > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/
> > macflightgear
> > co -P PLIB
> >
> > I will also commit the new macstart source soon.
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@flightgear.org
> > http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > 2f585eeea02e2c79d7b1d8c4963bae2d
>
> Arthur,
>
> I am building plib right now, and I got an error:
> 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 -c -o jsMacOSX.o `test -f 'jsMacOSX.cxx' || echo
> './'`jsMacOSX.cxx
> 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
>
>
> In your ReadMe on plib is says:
> NOTE: PLIB 1.8.4 does not build without making some changes in the
> code. In the CVS version as of 2005-11-04 a small change in
> jsMacOSX.cxx is needed.
>
> Can you give me more of a clue about the details of the change?  Can
> we get the change into plib?
>
> What I tried was just removing "static"  from line 278 and so far it
> got past that section, and is still compiling.
>
> I ended up building from the command line and I also hit a snag with
> pwMacOSX.cxx needed some compiler flags that were not set.
>
>
> --Adam
>
> ___
> Flightgear-devel mailing list
> Flightgear-devel@flightgear.org
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> 2f585eeea02e2c79d7b1d8c4963bae2d
>


--

- http://sourceforge.net/users/artooro/
- http://artooro.blogspot.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Adam Dershowitz]

--Adam



On Nov 14, 2005, at 7:23 AM, Arthur Wiebe wrote:

Please do commit them, I've had hand-rolled projects for all three  
for some
time, but they're out of sync. If I find any issues, I'll let you  
know.


James



OK, they are available now. I quickly wrote ReadMe's for them.

https://sourceforge.net/cvs/?group_id=126825

To checkout:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/ 
macflightgear

co -P flightgear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/ 
macflightgear

co -P SimGear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/ 
macflightgear

co -P PLIB

I will also commit the new macstart source soon.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Arthur,

I am building plib right now, and I got an error:
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 -c -o jsMacOSX.o `test -f 'jsMacOSX.cxx' || echo  
'./'`jsMacOSX.cxx
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


In your ReadMe on plib is says:
NOTE: PLIB 1.8.4 does not build without making some changes in the  
code. In the CVS version as of 2005-11-04 a small change in  
jsMacOSX.cxx is needed.


Can you give me more of a clue about the details of the change?  Can  
we get the change into plib?


What I tried was just removing "static"  from line 278 and so far it  
got past that section, and is still compiling.


I ended up building from the command line and I also hit a snag with  
pwMacOSX.cxx needed some compiler flags that were not set.



--Adam

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

 > Please do commit them, I've had hand-rolled projects for all three for some
> time, but they're out of sync. If I find any issues, I'll let you know.
>
> James
>

OK, they are available now. I quickly wrote ReadMe's for them.

https://sourceforge.net/cvs/?group_id=126825

To checkout:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P flightgear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P SimGear
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/macflightgear
co -P PLIB

I will also commit the new macstart source soon.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] XCode project files

[Ima Sudonim]

This would require someone to maintain the project files. I plan on
leaving the FlightGear project soon after the 0.9.9 release so
wouldn't be able to.



Arthur,

If the project files were in cvs, then you personally wouldn't have  
to maintain them. Whoever needed to use them would see about updating  
them so that others could use their work (in a perfect world). 8-)


I think it would avoid duplication of work -- i.e., multiple people  
each doing their own xcode file and make the work done like yours  
easier to find. At a minimum, maybe there could be a document  
pointing to the cygwin doc and your macflightgear project on  
sourceforge?


Personally, I think in the source tree is much easier to find...

Sorry to hear you're leaving after 0.9.9. Thanks for all the work  
you've put into flightgear!


Take care!

Ima

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] XCode project files

[Arthur Wiebe]

On 11/14/05, Ima Sudonim <[EMAIL PROTECTED]> wrote:
> > Please do commit them, I've had hand-rolled projects for all three
> > for some time, but they're out of sync. If I find any issues, I'll
> > let you know.
>
> Is it worth creating a developer directory under FlightGear CVS to
> contain things like these xcode project files and developer
> instructions for cygwin here  flightgear-users@flightgear.org/2485584.html> mentioned on the
> flightgear-user list or Norm's cygwin openal work (or at least a link
> to the current versions)?
>
> Maybe developer could have os-specific directories like macosx,
> cygwin, etc or just put everything in developer directory.
>
> These aren't utils and probably don't belong in the utils
> directory... but this would keep them in a standard place accessible
> to everyone from the source tree. It seems like we see similar
> problems that people are maintaining by themselves (projects (build
> files) for xcode and for MS visual C/C++ come to mind)
>
> thanks!
>
> Ima
>
>
>

This would require someone to maintain the project files. I plan on
leaving the FlightGear project soon after the 0.9.9 release so
wouldn't be able to. It just drains too much time. It was a good
experience though with making the mac version more user friendly.

I'll still commit the Xcode projects to macflightgear CVS later today
and then we'll see what happens.
https://sourceforge.net/cvs/?group_id=126825
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] XCode project files

[Ima Sudonim]

Please do commit them, I've had hand-rolled projects for all three
for some time, but they're out of sync. If I find any issues, I'll
let you know.


Is it worth creating a developer directory under FlightGear CVS to  
contain things like these xcode project files and developer  
instructions for cygwin here  mentioned on the  
flightgear-user list or Norm's cygwin openal work (or at least a link  
to the current versions)?


Maybe developer could have os-specific directories like macosx,  
cygwin, etc or just put everything in developer directory.


These aren't utils and probably don't belong in the utils  
directory... but this would keep them in a standard place accessible  
to everyone from the source tree. It seems like we see similar  
problems that people are maintaining by themselves (projects (build  
files) for xcode and for MS visual C/C++ come to mind)


thanks!

Ima



___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] XCode project files

[James Turner]

On 12 Nov 2005, at 14:30, Arthur Wiebe wrote:I've been using Xcode 2.2 for some time now building Flightgear and everything else. Preview builds until now of course.By the way Xcode projects you can use to build PLIB, Simgear, and FlightGear are available now. I've polished them up so they should be ready. If you're interested I'll commit them to the macflightgear cvs.Please do commit them, I've had hand-rolled projects for all three for some time, but they're out of sync. If I find any issues, I'll let you know.James -- You whine like a mule. You are still alive!  ___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d