[EMAIL PROTECTED] ha scritto: > Hi Doriano! > > I've kept that in mind. :-) ...during my investigations I always moved the > executable out of the project directory, so the compiler had to do it's job! > > It _seems_ to be like this: > 1) Open the old source in the gambas IDE > 2) Simply store it (there is no need to compile it) > 3) move the old executable (just for safeness) > 4) scp -r the whole project directory to the target machine > 5) ssh to the target machine > 6) gbc3 -va > 7) gba3 -v > ...and it works, like expected. > > I know this description differs a little bit from my last posting, but I came > to it, after I send my mail to the list. > > Only performing steps 6 and 7 (with svn from today) on the "old" sources on > the target machine, doesn't work. > > I fiddled hours and hours to get rid of this...and there are chances, that I > made something (anything??? :-) ) wrong...but I have another "clean" > machine, where I could verify this scenario. > Uhm... may be the compiler looks at the project source file? I see a .project file and, more likely, a .gambas directory where there seem to reside compiled files...
Cheers, Doriano ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Gambas-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gambas-user
