RE: [Flightgear-devel] Re: SimGear as shared lib

2005-05-09 Thread Richard Bytheway
Alex Romosan wrote: that was exactly the original problem: changes in simgear would involve a full recompilation of flightgear if you use static libraries. and compiling flightgear does take a very long time. now, if you use dynamic libraries, you can make your change in simgear and

[Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Melchior FRANZ
* Karsten Krispin -- Sunday 08 May 2005 02:30: just a small question: is it hard to include simgear as shared libs? When you want to change something in simgear you have to recompile fgfs. that needs pretty too long. Or is there a trick? No trick for avoiding to recompile fgfs, but for not

[Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Alex Romosan
Karsten Krispin [EMAIL PROTECTED] writes: yes. would be cool if you send me a patch. this is the patch: patch.simgear.bz2 Description: simgear as shared lib the last part gets simgear to use a system installed expat lib, so you might not want to apply it. after you apply the patch you need

[Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Alex Romosan
Martin Spott [EMAIL PROTECTED] writes: Hello Karsten, Karsten Krispin wrote: just a small question: is it hard to include simgear as shared libs? No, it's not dificult at all. But you probably don't _want_ to, because changes in FlightGear sometimes relate to changes in SimGear so you

Re: [Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Martin Spott
Alex Romosan wrote: that was exactly the original problem: changes in simgear would involve a full recompilation of flightgear if you use static libraries. Well, if you do substantial changes to SimGear that affects the headers, then you have to recompile the relating parts of FlightGear

Re: [Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Curtis L. Olson
Alex Romosan wrote: that was exactly the original problem: changes in simgear would involve a full recompilation of flightgear if you use static libraries. and compiling flightgear does take a very long time. now, if you use dynamic libraries, you can make your change in simgear and just go fly

Re: [Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Karsten Krispin
Am Sonntag 08 Mai 2005 19:33 schrieb Martin Spott: Alex Romosan wrote: that was exactly the original problem: changes in simgear would involve a full recompilation of flightgear if you use static libraries. Well, if you do substantial changes to SimGear that affects the headers, then you

Re: [Flightgear-devel] Re: SimGear as shared lib

2005-05-08 Thread Curtis L. Olson
Sorry, I normally wouldn't send corrections on my message but I made some lazy typos that make my message more confusing than it should have been. Let me try again ... Using static or dynamic libs really doesn't make that much difference when recompiling FlightGear. It is your installation

[Flightgear-devel] Re: SimGear as shared lib

2005-05-07 Thread Alex Romosan
Karsten Krispin [EMAIL PROTECTED] writes: just a small question: is it hard to include simgear as shared libs? When you want to change something in simgear you have to recompile fgfs. that needs pretty too long. i can send you a patch (i've been building simgear as shared libs for the

Re: [Flightgear-devel] Re: SimGear as shared lib

2005-05-07 Thread Karsten Krispin
Am Sonntag 08 Mai 2005 04:26 schrieben Sie: Am Sonntag 08 Mai 2005 03:22 schrieb Alex Romosan: Karsten Krispin [EMAIL PROTECTED] writes: just a small question: is it hard to include simgear as shared libs? When you want to change something in simgear you have to recompile fgfs. that