[Flightgear-devel] TerraGear Problem

2010-11-13 Thread J. Holden
Hi,

I'm using the most recent .exe build of TerraGear from the uni-duisburg website.

I believe I have followed all the steps properly to set up the work directory - 
I have run hgtchop, terrafit, genapts, and ogr-decode on everything, and have a 
work folder which appears to resemble what it should resemble.

However I am getting a problem with fgfs-construct when it goes to clip the 
shapefiles - the shapefiles should be properly clipped to each other already, 
but the program crashes immediately after it tries to clip the files for the 
first time.

I originally thought it was a problem with ocean - there is one tile in the 
scenery build which is all ocean (it's a 2x4 degree build) and even after 
removing that from the cycle it still crashes on first instance.

I have no idea what the exact error is because this is an executable on Windows 
XP and the error crash doesn't give you any good information on what happened.

How might I fix this problem, not including compiling the program myself?

Cheers
John

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread Gene Buckle
On Sat, 13 Nov 2010, James Turner wrote:

>
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>
>> My personal rule-of-thumb is to only commit when I've got time to watch the 
>> Hudson board go green - it's on an hourly poll at the moment, though we can 
>> allow other users to manually kick off builds, if you ask Gene nicely.
>>
>> How do you get a change over to hudson before committing it to git?  (maybe 
>> a dumb question?)
>
> Ah, sorry to disappoint, but you have to commit to Git first - unlike 
> some setups, we haven't engineered a 'compile before publish' system. 
> Hence my ensuring I have time to watch Hudson *after* a commit, and, for 
> example, make a fix commit if I broke something.

What about offering those with commit rights the ability to trigger builds 
on their own?  That way if they break it, they can fix it and re-start the 
build.  I've enabled the "email the person that broke the build" option, 
but I don't know how correctly that works yet.

g.


-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.simpits.org/geneb - The Me-109F/X Project

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

Political correctness is a doctrine, fostered by a delusional, illogical
minority, and rabidly promoted by an unscrupulous mainstream media, which
holds forth the proposition that it is entirely possible to pick up a turd
by the clean end.

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Solved: FGFS from GIT fails to compile

2010-11-13 Thread Mike
Dear List,

thanks to James the issue of fgfs not compiling due to a missing reference is 
not sucking any more after push ff979312 :o)

Cheers,
Mike

--- If you want to be understood, you first have to listen ---



--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] METAR stopped working

2010-11-13 Thread ThorstenB
> Unfortunately this means METAR is broken (probably permanently) for
> all previous FG versions now...

As a follow-up to the METAR issue: there actually is a workaround for
FG 1.9.x and 2.0 - by using a proxy server. The requests sent by FG to
a configured proxy server are fine. And the actual HTTP request for
the weather server is then generated by the proxy - which, of course,
also works. So this revives METAR for older FG versions.
Only takes a valid proxy server given to the fgfs command-line. More
details in the forum:
http://www.flightgear.org/forums/viewtopic.php?t=10002

cheers,
Thorsten

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread James Turner

On 13 Nov 2010, at 19:36, Tim Moore wrote:

> There's never been a guarantee that the development sources compile for 
> everybody at all moments. That's why they are development sources. I 
> appreciate the Hudson process and quite often the change to get things 
> compiling on a given platform are obvious, but sometimes they aren't and one 
> needs to rely on the help of those who know the other platforms better. I 
> don't see why they would have get their own copy of the offending source code 
> from anywhere other than the "next" branch.

I tend to agree - I understand why processes such as that proposed by Alex make 
sense where the cost of breakage is very high, but with our number of 
developers and commit rate, I think a high-powered 'revert bad commits' system 
will generate more hassle than it avoids.

James


--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread Tim Moore
There's never been a guarantee that the development sources compile for
everybody at all moments. That's why they are development sources. I
appreciate the Hudson process and quite often the change to get things
compiling on a given platform are obvious, but sometimes they aren't and one
needs to rely on the help of those who know the other platforms better. I
don't see why they would have get their own copy of the offending source
code from anywhere other than the "next" branch.

Tim

On Sat, Nov 13, 2010 at 5:57 PM, Alex Perry  wrote:

> On Sat, Nov 13, 2010 at 7:35 AM, Arnt Karlsen  wrote:
> > On Sat, 13 Nov 2010 09:57:14 +, James wrote in message
> >> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
> >> > My personal rule-of-thumb is to only commit when I've got time to
> >> > watch the Hudson board go green - it's on an hourly poll at the
> >> > moment, though we can allow other users to manually kick off
> >> > builds, if you ask Gene nicely.
> >>
> >> Ah, sorry to disappoint, but you have to commit to Git first - unlike
> >> some setups, we haven't engineered a 'compile before publish' system.
> >> Hence my ensuring I have time to watch Hudson *after* a commit, and,
> >> for example, make a fix commit if I broke something.
> >
> > ..an idea; a bad commit that doesn't compile successfully,
> > can it be reverted automatically?  That way git would stay
> > unbroken, until new unbroken code is added etc and compiles
> > successfully.
>
> I like automatic build systems which, if ..
> * a commit fails to build for any platform,
> * the prior build passed for every platform,
> * only one commit happened in that time,
> * the word "CRITICAL" is nowhere in the change description,
> ... automatically rolls back ... and tells someone.
>
> As a bonus, if it fails at the third bullet, it can automatically
> submit builds for all the intervening releases in an attempt to make
> the bullet pass.
>
> As another bonus, after the rollback, the fifth bullet looks back at
> the first bullet to see whether it failed to build for every platform
> and, if so, it would be nice for someone to be notified.
>
>
> --
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] FG/OSG warping software help

2010-11-13 Thread castle
Hi,

Have been working on image warping software in OSG to add some capability
for additional screen geometries.

With new capabilities and lower costs in graphics and projectors, wide
view panoramic immersive simulations are becoming the norm. Adding this
capability to FG would be a big plus.

If you care to pitch in, contact me via PM or this website and I'll send
you some pics and details of the current state.

As you will see, it needs some work integrating into the FG scene graph --
an area where my eyes glaze over ;-),  eventually I'll figure it out, but
if there is anyone willing to help out it would be appreciated. The
immediate problem is to get the OSG warping capability integrated into the
scene graph.

Tim Moore has been helping with tips and advice but like so many of us,
there are always competing priorities and committments.  The near term
goal has been to get a working solution for a multi-display capability
integrated into
flightgear.

We're close

Thanks
Jack








--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread Alex Perry
On Sat, Nov 13, 2010 at 7:35 AM, Arnt Karlsen  wrote:
> On Sat, 13 Nov 2010 09:57:14 +, James wrote in message
>> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>> > My personal rule-of-thumb is to only commit when I've got time to
>> > watch the Hudson board go green - it's on an hourly poll at the
>> > moment, though we can allow other users to manually kick off
>> > builds, if you ask Gene nicely.
>>
>> Ah, sorry to disappoint, but you have to commit to Git first - unlike
>> some setups, we haven't engineered a 'compile before publish' system.
>> Hence my ensuring I have time to watch Hudson *after* a commit, and,
>> for example, make a fix commit if I broke something.
>
> ..an idea; a bad commit that doesn't compile successfully,
> can it be reverted automatically?  That way git would stay
> unbroken, until new unbroken code is added etc and compiles
> successfully.

I like automatic build systems which, if ..
* a commit fails to build for any platform,
* the prior build passed for every platform,
* only one commit happened in that time,
* the word "CRITICAL" is nowhere in the change description,
... automatically rolls back ... and tells someone.

As a bonus, if it fails at the third bullet, it can automatically
submit builds for all the intervening releases in an attempt to make
the bullet pass.

As another bonus, after the rollback, the fifth bullet looks back at
the first bullet to see whether it failed to build for every platform
and, if so, it would be nice for someone to be notified.

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] FGFS from GIT fails to compile

2010-11-13 Thread Mike
Dear List,

I'm regularly updating my installation from GIT (Ubuntu x64 2.6.32-26). Last 
compile run with sources of last weekend worked fine. Today I wanted to renew 
my stuff but run into an error during compile. Maybe someone knows what 
happens. I'm puzzled as Hudson looks fine...

Suspicious output:

make[2]: Betrete Verzeichnis '/home/user/fgfs/fgfs/flightgear/src/Main'
g++ -DPKGLIBDIR=\"/home/user/fgfs/install/fgfs/share/FlightGear\" -g -O2 -Wall 
-I/home/user/fgfs/install/simgear -D_REENTRANT   
-L/home/user/fgfs/install/simgear/lib -L/home/user/fgfs/install/plib/lib 
-L/usr/local/lib -L/home/user/fgfs/install/simgear/lib 
-L/home/user/fgfs/install/plib/lib -L/usr/local/lib -o fgfs bootstrap.o 
libMain.a ../../src/Aircraft/libAircraft.a  ../../src/Cockpit/libCockpit.a 
../../src/Cockpit/built_in/libBuilt_in.a ../../src/Network/libNetwork.a 
../../src/FDM/libFlight.a ../../src/FDM/ExternalNet/libExternalNet.a 
../../src/FDM/ExternalPipe/libExternalPipe.a ../../src/FDM/JSBSim/libJSBSim.a 
../../src/FDM/JSBSim/initialization/libInit.a 
../../src/FDM/JSBSim/models/libModels.a 
../../src/FDM/JSBSim/models/flight_control/libFlightControl.a 
../../src/FDM/JSBSim/models/atmosphere/libAtmosphere.a 
../../src/FDM/JSBSim/models/propulsion/libPropulsion.a 
../../src/FDM/JSBSim/input_output/libInputOutput.a 
../../src/FDM/JSBSim/math/libMath.a
 ../../src/FDM/YASim/libYASim.a ../../src/FDM/LaRCsim/libLaRCsim.a 
../../src/FDM/UIUCModel/libUIUCModel.a ../../src/FDM/SP/libSPFDM.a 
../../src/GUI/libGUI.a ../../src/Autopilot/libAutopilot.a 
../../src/Input/libInput.a ../../src/Instrumentation/KLN89/libKLN89.a 
../../src/Instrumentation/libInstrumentation.a 
../../src/Instrumentation/HUD/libHUD.a ../../src/Model/libModel.a 
../../src/Navaids/libNavaids.a ../../src/Scenery/libScenery.a 
../../src/Scripting/libScripting.a ../../src/Sound/libSound.a 
../../src/Airports/libAirports.a ../../src/MultiPlayer/libMultiPlayer.a 
../../src/AIModel/libAIModel.a ../../src/ATC/libATC.a 
../../src/Systems/libSystems.a ../../src/Time/libTime.a 
../../src/Traffic/libTraffic.a ../../src/Environment/libEnvironment.a -lsgroute 
-lsgsky -lsgsound -lsgephem -lsgtgdb -lsgmodel -lsgbvh -lsgmaterial -lsgutil 
-lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgprops -lsgdebug -lsgmagvar 
-lsgmisc -lsgnasal -lsgxml -lsgsound -lsgserial
 -lsgstructure -lsgenvironment -lplibpuaux -lplibpu -lplibfnt -lplibjs -lplibsg 
-lplibul   -lpthread   -lz -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE -lXi -lXext 
-lX11 -lrt -ldl -lm  -lalut -lopenal -lrt -ldl -lm   -lpthread  -ldbus-1 -lhal 
-losgFX -losgParticle -losgSim -losgViewer -losgGA -losgText -losgDB -losgUtil 
-losg -lOpenThreads -ljpeg 
libMain.a(fgviewer.o): In function `Options':
/home/user/fgfs/install/OpenSceneGraph/include/osgDB/Options:109: undefined 
reference to `osgDB::Options::parsePluginStringData(std::basic_string, std::allocator > const&, char, char)'
libMain.a(splash.o): In function `fgCreateSplashCamera':
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:292: undefined reference to 
`osgText::TextBase::setFont(std::basic_string, 
std::allocator > const&)'
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:293: undefined reference to 
`osgText::TextBase::setCharacterSize(float)'
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:302: undefined reference to 
`osgText::TextBase::setFont(std::basic_string, 
std::allocator > const&)'
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:303: undefined reference to 
`osgText::TextBase::setCharacterSize(float)'
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:313: undefined reference to 
`osgText::TextBase::setFont(std::basic_string, 
std::allocator > const&)'
/home/user/fgfs/fgfs/flightgear/src/Main/splash.cxx:314: undefined reference to 
`osgText::TextBase::setCharacterSize(float)'
../../src/Instrumentation/libInstrumentation.a(wxradar.o): In function 
`osgText::TextBase::setFont(osgText::Font*)':
/home/user/fgfs/install/OpenSceneGraph/include/osgText/TextBase:43: undefined 
reference to `osgText::TextBase::setFont(osg::ref_ptr)'
../../src/Instrumentation/libInstrumentation.a(wxradar.o): In function 
`wxRadarBg::update_data(SGPropertyNode const*, double, double, double, double, 
bool)':
/home/user/fgfs/fgfs/flightgear/src/Instrumentation/wxradar.cxx:566: undefined 
reference to `osgText::TextBase::setCharacterSize(float)'
../../src/Scenery/libScenery.a(tilemgr.o): In function `Options':
/home/user/fgfs/install/OpenSceneGraph/include/osgDB/Options:109: undefined 
reference to `osgDB::Options::parsePluginStringData(std::basic_string, std::allocator > const&, char, char)'
/home/user/fgfs/install/simgear/lib/libsgtgdb.a(TileEntry.o): In function 
`simgear::TileEntry::loadTileByFileName(std::basic_string, std::allocator > const&, osgDB::Options const*)':
TileEntry.cxx:(.text+0x2797): undefined reference to 
`osgDB::Options::parsePluginStringData(std::basic_string, std::allocator > const&, char, char)'
/home/user/fgfs/install/simgear/lib/lib

Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread Arnt Karlsen
On Sat, 13 Nov 2010 09:57:14 +, James wrote in message 
<0275fe52-84ce-4e88-a29c-b1382f3ae...@mac.com>:

> 
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
> 
> > My personal rule-of-thumb is to only commit when I've got time to
> > watch the Hudson board go green - it's on an hourly poll at the
> > moment, though we can allow other users to manually kick off
> > builds, if you ask Gene nicely.
> > 
> > How do you get a change over to hudson before committing it to
> > git?  (maybe a dumb question?)
> 
> Ah, sorry to disappoint, but you have to commit to Git first - unlike
> some setups, we haven't engineered a 'compile before publish' system.
> Hence my ensuring I have time to watch Hudson *after* a commit, and,
> for example, make a fix commit if I broke something.

..an idea; a bad commit that doesn't compile successfully, 
can it be reverted automatically?  That way git would stay 
unbroken, until new unbroken code is added etc and compiles 
successfully.


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread Curtis Olson
On Sat, Nov 13, 2010 at 3:57 AM, James Turner wrote:

>
> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
>
> > My personal rule-of-thumb is to only commit when I've got time to watch
> the Hudson board go green - it's on an hourly poll at the moment, though we
> can allow other users to manually kick off builds, if you ask Gene nicely.
> >
> > How do you get a change over to hudson before committing it to git?
>  (maybe a dumb question?)
>
> Ah, sorry to disappoint, but you have to commit to Git first - unlike some
> setups, we haven't engineered a 'compile before publish' system. Hence my
> ensuring I have time to watch Hudson *after* a commit, and, for example,
> make a fix commit if I broke something.


Ok, I see ... misread your original statement.

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org -
http://www.flightgear.org/blogs/category/curt/
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Segmentation fault in fgrun

2010-11-13 Thread fierst42
Yes. Confirmed.

Thanks Fred.



Op 13-11-10 11:02, Frederic Bouvier schreef:
> It should be fixed now.
> Regards,
> -Fred
>
>


--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FlightProSim advert on FaceBook

2010-11-13 Thread Arnt Karlsen
On Fri, 12 Nov 2010 16:21:41 -0800 (PST), Chris wrote in message 
<429654.31507...@web56904.mail.re3.yahoo.com>:

> Another avenue I have considered is a New Zealand consumer affairs
> program named "Fair Go". This TV show has an excellent track record
> of exposing scammers, and sticking up for those who are being shafted
> by scammers. The format is a group of presenters who research claims
> of unfair treatment, then in many cases try to confront the scammers
> - thats the part where the scammers usually turn tail and run or get
> aggro towards the camera. Quite often however the scammers cave in to
> the unwanted media pressure and relent, paying back money they've
> misappropriated, or as the name of the program suggests, delivering a
> "Fair Go". Those extra prickly scammers who outright refuse often
> find themselves in court, as the Fair Go team have a number of legal
> guys at their disposal, to advise on cases considered worthy of
> elevating to the law courts.
> 
> Fair Go have taken on anyone from dodgy car dealers, to Microsoft. If
> the team at Fair Go think it is a case worthy of pursuing, they'll do
> it with gusto, harassing scammers, and making a laughing stock of
> them on TV. Not good PR for the scammers.
> 
> Check out youtube clips with a search "fair go nz" to see how the
> show operates.
> 
> Regards,
> 
> Chris Wilkinson, YBBN/BNE.

..now we're getting constructive. ;o)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] FlightProSim advert on FaceBook

2010-11-13 Thread Arnt Karlsen
On Sat, 13 Nov 2010 09:26:07 +0800, Innis wrote in message 
:

> 
> 
> 
> 
> Hi Chris
> 
> I would let it go mate. While I feel no better about people making
> money off my work I also feel that it is pretty much or own fault.

..you are here giving him a license to carry on.  While you are
entitled to license out your own works as you please, you would
need the other peoples license to license out their works.

> The only way you are going to stop this guy is to make it a pain in
> the arse for him. Until we are prepared to fight fire with fire by
> releasing our own commercial copy  then he has an open field. With
> the depth of talent we have here surely we could come up with a water
> making system that causes him some headaches.Even if it only causes
> him to spend an hour extra each time. While we sit and belly ache
> about it he will just continue so the ball is in our court.
> 
> Cheers
> Innis
> 
> 


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Segmentation fault in fgrun

2010-11-13 Thread Frederic Bouvier
...
> 6) Click Input/Output (it shows
> "--generic=socket,out,10,localhost,16661, udp,fgcom", which is
> io-item-1 in the settings file)
> 7) Click on "--generic=socket,out,10,localhost,16661, udp,fgcom"
> 8) BOOM, Segmentation fault (core dumped). There is no time to click
> Delete or OK, it just immediately crashes as soon as I click the
> parameter.

It should be fixed now.

Regards,
-Fred

-- 
Frédéric Bouvier
http://my.fotolia.com/frfoto/  Photo gallery - album photo
http://www.youtube.com/user/fgfred64   Videos


--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Hey Curt... :)

2010-11-13 Thread James Turner

On 12 Nov 2010, at 23:44, Curtis Olson wrote:

> My personal rule-of-thumb is to only commit when I've got time to watch the 
> Hudson board go green - it's on an hourly poll at the moment, though we can 
> allow other users to manually kick off builds, if you ask Gene nicely.
> 
> How do you get a change over to hudson before committing it to git?  (maybe a 
> dumb question?)

Ah, sorry to disappoint, but you have to commit to Git first - unlike some 
setups, we haven't engineered a 'compile before publish' system. Hence my 
ensuring I have time to watch Hudson *after* a commit, and, for example, make a 
fix commit if I broke something.

James


--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel