waldo kitty wrote: > Martin Friebe wrote: > >> but a couple of thinks that come to mind: >> 1) What version of FPC are you using (you only said you updated >> Lazarus); you refer to FPC 2.2.2, have you tried the fixes branch >> (2.2.3)? or trunc(2.3.1)? >> > > i'm using whatever comes with lazarus... i started with laz 0.9.26 and then > completely removed it to install 0.9.27 because i found that some config > settings are evidently hardcoded or shared in a/the registry when a dual > install > of 0.9.27 still had some things pointing to the old 0.9.26 stuffs :? :( > On the daily snapshot page, you get a windows build with fpc 2.2.2 and another one with 2.2.3 (eq fixes branch of fpc)
lookup -pcp (--primar-config-path) Lazarus does what a windows app should do, it stores setting in you users home director (depends on windows version) Then if you installed Lazarus (incl fpc) in one directory => do not rename the directory; otherwise you must update you fpc.cfg file (windows search to locate) If you have multiply installations, you may have to go to environment->options, and adapt the path to fpc (once you use -pcp) > and that might be another "bug" or something where one can't install laz > 0.9.26 > to one directory and 0.9.27 to another and have each come out of the box > without > sharing any config settings or something... i dunno, as i'm still trying to > come > to grips with the whole GUI interface and drop this here and that there to > create a "hello world!" GUI app that's 10Meg (tongue in cheek!) in size > compared > to a textmode version that's only 2K ;) :lol: > use strip to get rid of the symbols (or compiler options dialog, unclick all the debug info) But leave it in while looking for a bug > >> 2) You say you do not know the exact error: " because the popup box >> doesn't state it" => Try running the exe in the debugger, make sure you >> compile with debug symbols for gdb (-g, maybe also -gl). >> > > i've not changed any settings from the defaults on install... i have, a few > times, run some stuff directly from the GUI in the debugger but even with > 256Meg > of RAM in this box, it gets a bit on the tight side at times which is why i > switched over to simply building the apps and then shutting down laz and > running > the built code outside on its own... maybe that wasn't/isn't such a good idea? > why not, but it doesn't help debugging (unless you do gdb by hand) _______________________________________________ Lazarus mailing list [email protected] http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
