Re: [lazarus] Bugs ? Startlazarus increases link times
Right, I can't be certain the drive is fine of course, but it is brand new - I've have this laptop less than a month. It isn't a great work horse but it's all I got until my desktop CPU comes back from repairs. That said, dmesg and messages are both empty, and it does finish, machine has 180mb of ram. A.J. -- A.J. Venter Chief Software Architect OpenLab International http://www.getopenlab.com http://www.silentcoder.co.za _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
On Tue, 30 Aug 2005, Tony Pelton wrote: hi all, interestingly, with what i _think_ is the same basic set of compiler flags for debug and optimizations etc ... the DLL from lazarus comes out about 4x as large. First off, try to look at the uses clause of your main source file. if it contains something like 'interfaces', remove it. anyway ... when the flight simulator loads the DLL from lazarus, it spits out an error message telling me that the DLL isn't a DLL. Show Options for the compiler in the IDE says : snip -Sd -Cirot -TWin32 -gl -vewnhi -l -FuX:\XPSDK102\Delphi\XPLM\ -Fu. -oX:\src\x-pascal\xsa.exe /snip Remove the -gl (switch off debug info in Project|Compiler options, tab linking), and set the output name to xsa.dll, because it is creating an exe. (Project|project options, tab application, Target file) Also, disable the 'Win32 GUI application' under Project|Compiler options, tab linking i'm not too sure about the -o option ? the compiler is clearly spitting out xsa.dll instead of xsa.exe. presumably this is because the source file has the library directive ? Probably, yes. Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Esthetics Windows Patch
Hi, a made a esthetics patch that set the borderStyle propertie to bsSizeToolWin For the Code Explorer , The Object Inspector and the Message windows It's a simple hack that give better looking windows and i tested it for the win32 platform Second i wanna know what the docking system miss in win32 I know that docking work in linux but not working in win32 Thanks Christian Fillion bsSizeToolWin.diff Description: Binary data
Re: [lazarus] Lazarus / C++ Application Released
On 8/29/05, Chris Gordon-Smith [EMAIL PROTECTED] wrote: Hullo All This is to announce the release of version 0.2 of my SimSoup Artificial Chemistry simulator program. As far as I am aware, this is the first program that combines use of the Lazarus Component Library (LCL) for the presentation of the user interface with C++ for other program logic. The integration of C++ with Lazarus / FPC provides a programming environment similar to that of C++ Builder (version 0.1 of the program was developed with C++ Builder). For screenshots see:- http://www.simsoup.info/SimSoup_Screenshot.html I will welcome any feedback at the email address mentioned on my Home page (see below). How did you call the C++ code from FPC or did you do only from C++ to FPC ? Razvan _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus / C++ Application Released
On 8/30/05, Razvan Adrian Bogdan [EMAIL PROTECTED] wrote: On 8/29/05, Chris Gordon-Smith [EMAIL PROTECTED] wrote: Hullo All This is to announce the release of version 0.2 of my SimSoup Artificial Chemistry simulator program. As far as I am aware, this is the first program that combines use of the Lazarus Component Library (LCL) for the presentation of the user interface with C++ for other program logic. The integration of C++ with Lazarus / FPC provides a programming environment similar to that of C++ Builder (version 0.1 of the program was developed with C++ Builder). For screenshots see:- http://www.simsoup.info/SimSoup_Screenshot.html I will welcome any feedback at the email address mentioned on my Home page (see below). How did you call the C++ code from FPC or did you do only from C++ to FPC ? Opps i just saw on your website, verry nice project. Razvan _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
Marc Weustink wrote: Vincent Snijders wrote: Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. AFAIK you can wait for file handles, but not for pipe handles. AFAIK we wait here for pipehandles all the time And how are you doing that? In lazarus the following code is used (more or less): repeat Windows.PeekNamedPipe(PipeHnd, nil, 0, nil, @TotalBytesAvailable, nil); if TotalBytesAvailable0 then break; Application.ProcessMessages Sleep(10); until false; IMHO, that is not really waiting. Vincent. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005, Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: On Tue, 30 Aug 2005, Micha Nelissen wrote: What do you mean with Idle handler? TApplication.OnIdle ? In any sane app, that is only called once when the user goes idle; after that, the app is blocked waiting for user input. Hm. So that is not usable. On Unix, it's easy: I once wrote a GTK version of a debug server. You can tell GTK to watch for input on a file descriptor in it's main loop. If there is input on your descriptor, a callback you specify is called. Yes, this is used in the gtk widgetset interface in the LCL too, now; that's what WakeMainThread does there (send a byte down that pipe). In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. OTOH, the backend of the IPC server will use messages to copy things around ? So the message queue would be woken up that way. Yes. (Why they made this two separate functions is a mystery to me, it makes things horribly complicated...) Some threads have no message queue, so MsgWait... is more expensive, would require a message queue to be created. So in fact, what we'd need is a pair of calls in TApplication : TApplication.AddWatch(AHandle: THandle; Handler : TNotifyEvent); TApplication.RemoveWatch(AHandle: THandle); Which would handle both things transparantly in the message loop. (the standard IsWindow function of Windows could be used to determine what kind of handle it is in a windows app) This would come in handy in many applications. Hmm, I'm not sure. Can you give examples? A THandle is a widget-specific thingy, it doesn't have the same semantics on various platforms, so it's not directly usable by users of LCL (if you want one source code base). Things you could use this function for: file change notifications, events, ... all have to be seperately implemented in the FCL/LCL to make them work universally and well. Seems so, yes. Sebastian Guenther once started such a thing (fpAsync) but never managed to get the windows side of things working, exactly because of the different types of handle. Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. AFAIK you can wait for file handles, but not for pipe handles. Vincent. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005, Vincent Snijders wrote: Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. AFAIK you can wait for file handles, but not for pipe handles. You can wait on any handle: file, pipe, socket. From msdn: The WaitForSingleObject function can wait for the following objects: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer The MsgWaitForMultipleObjects function can specify handles of any of the following object types in the pHandles array: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005 12:20:40 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: You can wait on any handle: file, pipe, socket. From msdn: The WaitForSingleObject function can wait for the following objects: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer Well, I don't see neither file, nor pipe, nor socket in this list. (That's why I made that specific comment, earlier). The documentation says waiting for file and pipe handles works in some circumstances but it should not be used. Micha _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Localize.bat
On 8/29/05, Vincent Snijders [EMAIL PROTECTED] wrote: Razvan Adrian Bogdan wrote: I have made a script for windows similar to localize.sh, i thought some other translators might want it, it does the same thing as the linux version. Please rename the attached file (funy mail protections). If someone wants a good crossplatform editor for the files try http://www.poedit.org I tested this script and found two issues: 1. Because I didn't have a updatepofiles.exe, it entered the tools subdir and there the makefile was regenerated several times. Here follows a snippet from the make output: make[1]: Entering directory `C:/lazarus/source/lazarus/tools' /fpc/2.0.0/bin/i386-win32/fpcmake.exe -w Processing Makefile.fpc i386-win32 requires: rtl,paszlib,netdb,fcl,pasjpeg,ibase,postgres,mysql,sqlite, libasync Writing Makefile I have no idea, why the makefile should be regenerated. 2. It creates patches for existing po files, which it shouldn't, afaics. Example: Index: lcl/languages/lcl.po === --- lcl/languages/lcl.po(revision 7592) +++ lcl/languages/lcl.po(working copy) @@ -79,7 +79,7 @@ msgstr #: lclstrconsts:rsfdfilealreadyexists -msgid The file \%s\ already exists.\015Overwrite ? +msgid The file \%s\ already exists.Overwrite ? msgstr #: lclstrconsts:rsfdpathmustexist Aparently the #13 is converted to \015 in the messageid on linux, but it is ignored on win32. But it only happens for this particular resourcestring, lclstrconsts:rsfdfilealreadyexists, but in all languages. This is really verry strange, if you have a look in the script you can see it doesn't do much by itself, instead it relies on make to do the compilation and rstconv to prepare the po skeleton and updatepofiles to update all po files to the most recent version of the po generated by rstconv, there should be no reason for it to do this. Manually typing the commands found in the script should have the same effect as the script itself wich does nothing directly, exactly like the linux version. The only problem is that programmers would rather not type the commands manually for all the language sections so i made this script. Razvan _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: On Tue, 30 Aug 2005, Micha Nelissen wrote: What do you mean with Idle handler? TApplication.OnIdle ? In any sane app, that is only called once when the user goes idle; after that, the app is blocked waiting for user input. Hm. So that is not usable. On Unix, it's easy: I once wrote a GTK version of a debug server. You can tell GTK to watch for input on a file descriptor in it's main loop. If there is input on your descriptor, a callback you specify is called. Yes, this is used in the gtk widgetset interface in the LCL too, now; that's what WakeMainThread does there (send a byte down that pipe). In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. OTOH, the backend of the IPC server will use messages to copy things around ? So the message queue would be woken up that way. (Why they made this two separate functions is a mystery to me, it makes things horribly complicated...) Some threads have no message queue, so MsgWait... is more expensive, would require a message queue to be created. So in fact, what we'd need is a pair of calls in TApplication : TApplication.AddWatch(AHandle: THandle; Handler : TNotifyEvent); TApplication.RemoveWatch(AHandle: THandle); Which would handle both things transparantly in the message loop. (the standard IsWindow function of Windows could be used to determine what kind of handle it is in a windows app) This would come in handy in many applications. Hmm, I'm not sure. Can you give examples? A THandle is a widget-specific thingy, it doesn't have the same semantics on various platforms, so it's not directly usable by users of LCL (if you want one source code base). Things you could use this function for: file change notifications, events, ... all have to be seperately implemented in the FCL/LCL to make them work universally and well. Micha _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
Vincent Snijders wrote: And how are you doing that? In lazarus the following code is used (more or less): repeat Windows.PeekNamedPipe(PipeHnd, nil, 0, nil, @TotalBytesAvailable, nil); if TotalBytesAvailable0 then break; Application.ProcessMessages Sleep(10); until false; Shouldn't a sleep(1) or sleep(0) make things more responsive? Giving up the current time slice is usually enough to make a thread consuming virtually zero cpu load. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
Micha Nelissen wrote: On Tue, 30 Aug 2005 12:23:06 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: Things you could use this function for: file change notifications, events, ... all have to be seperately implemented in the FCL/LCL to make them work universally and well. Seems so, yes. Sebastian Guenther once started such a thing (fpAsync) but never managed to get the windows side of things working, exactly because of the different types of handle. Hmm, is this work published somewhere? http://svn.freepascal.org/svn/fpc/trunk/fcl/inc/fpasync.pp _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
Vincent Snijders wrote: Marc Weustink wrote: Vincent Snijders wrote: Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. AFAIK you can wait for file handles, but not for pipe handles. AFAIK we wait here for pipehandles all the time And how are you doing that? In lazarus the following code is used (more or less): repeat Windows.PeekNamedPipe(PipeHnd, nil, 0, nil, @TotalBytesAvailable, nil); if TotalBytesAvailable0 then break; Application.ProcessMessages Sleep(10); until false; IMHO, that is not really waiting. Nope. I dived a bit into it, it is not really my code. I think you create a wait with the following concept, using overlapped IO Use ReadFileEx(hPipe, buf, nNumberOfBytesToRead, lpOverlapped, lpCompletionRoutine) to read from the pipe. Then call MsgWaitForMultipleObjectEx to enter an alertable wait state In the lpCompletionRoutine you can set an event to signal that the pipe read is finished. Hmm... now I notice that this is NT+ only :( Marc _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005, Micha Nelissen wrote: On Tue, 30 Aug 2005 12:20:40 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: You can wait on any handle: file, pipe, socket. From msdn: The WaitForSingleObject function can wait for the following objects: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer Well, I don't see neither file, nor pipe, nor socket in this list. (That's why I made that specific comment, earlier). The documentation says waiting for file and pipe handles works in some circumstances but it should not be used. It works. They even forgot to mention sockets. The point is that it interferes with the message queue. in other words, while using WaitForSingleObject(), your app will not respond to messages. That is why they recommend MsgWaitForMultipleObjects(), this should work on both, and will warn about files and about arrived messages. In each case, I have everything working now both on Windows and Linux, both command-line and GUI apps. I'll commit the SimpleIPC implementation in the FCL. I can send the rest (GUI demo apps debugserver stuff) to the lazarus team, if they want. Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005, Vincent Snijders wrote: Michael Van Canneyt wrote: On Tue, 30 Aug 2005, Vincent Snijders wrote: Micha Nelissen wrote: On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: In windows, it's slightly more difficult (surprise, surprise :-) ) You can use MsgWaitForMultipleObjects to do this for a windows handle, or use WaitForSingleObject on a simple file handle. You can't wait for file handles in windows. AFAIK you can wait for file handles, but not for pipe handles. You can wait on any handle: file, pipe, socket. From msdn: The WaitForSingleObject function can wait for the following objects: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer The MsgWaitForMultipleObjects function can specify handles of any of the following object types in the pHandles array: * Change notification * Console input * Event * Job * Memory resource notification * Mutex * Process * Semaphore * Thread * Waitable timer Didn't you notice pipe is missing in both lists? Or is pipe called differently? Both pipes and TCP/IP sockets are missing in this list. Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Simple IPC implementation.
On Tue, 30 Aug 2005, Micha Nelissen wrote: On Tue, 30 Aug 2005 12:23:06 +0200 (Romance Daylight Time) Michael Van Canneyt [EMAIL PROTECTED] wrote: Things you could use this function for: file change notifications, events, ... all have to be seperately implemented in the FCL/LCL to make them work universally and well. Seems so, yes. Sebastian Guenther once started such a thing (fpAsync) but never managed to get the windows side of things working, exactly because of the different types of handle. Hmm, is this work published somewhere? Yes. fcl/inc/fpasync.pp packages/base/libasync Michael. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
On Tue, 30 Aug 2005 10:18:41 -0400 Tony Pelton [EMAIL PROTECTED] wrote: the message produced by the flight simulator lists a missing DLL as one of the possible reasons for not being able to load the DLL, along with the it isn't a DLL reason. thanks for any help. Have you tried opening the DLL in Dependency Walker or some alike tool ? Micha _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
On Tue, 30 Aug 2005 10:52:05 -0400 Tony Pelton [EMAIL PROTECTED] wrote: On 8/30/05, Micha Nelissen [EMAIL PROTECTED] wrote: On Tue, 30 Aug 2005 10:18:41 -0400 Tony Pelton [EMAIL PROTECTED] wrote: Have you tried opening the DLL in Dependency Walker or some alike tool ? did you mean this tool ? http://www.dependencywalker.com/ i hadn't used this before. i dl'ed it and fired it up. i _think_ i basically understand what it is telling me. in both cases, i see dependencies on the usual DLL's (GDI32, KERNEL32, USER32). nothing suspicious looking, at least to my untrained eyes on any other DLL's. Well, if it would depend on non-existing things (as suggested by an error message?), you would see right away. i also see my exports in the DLL. so ... i haven't yet asked the obvious question : Do people _know_ that Lazarus can be used to generate clean DLL's on windows that are NOT GUI applications ? Can lazarus be used as a plain 'ole IDE for DLL development ? It whould be, but I think not a lot of people have tried to do this yet. (Me neither, btw). What commandline options does FP hand to fpc to compile it, and what is the difference to the commandline lazarus generates ? Micha _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
On 8/30/05, Florian Klaempfl [EMAIL PROTECTED] wrote: Tony Pelton wrote: Using FP makes me suicidal. Strange, almost the whole compiler is developed using fp :) hi florian, first, thanks for the response and all of the great work on free pascal. as to my comment about being suicidal ... actually, i was trying to be funny. truthfully, i actually _do_ like the FP IDE, and was mostly happy using it because it is simple and lightweight, and I had been using it for a few months. I went in search of a better solution because there are some usability issues that were getting in the way of my productivity and were making my wrists hurt. a) it would be nice if the IDE had support for a wider range of sizes, rather than just 80x[25|50] b) more useable file dialogs ( opening files is cumbersome ) c) find identifier support like in lazarus d) better code completion e) better mouse support (for cursor positioning mostly) f) better tab/spaces/indent support g) i _think_ there are some bugs with using different .ini files for storing different IDE configurations. it has been a few months since i tried this last, but i think the command line switch for loading .ini files doesn't work, and the IDE doesn't remember the last used ini configuration ? ... and probably my #1 complaint h) use windows conventions for cut/copy/paste ctrl-key combos ! anyhow ... fwiw i've actually been doing a *little* poking around in the FP source ... and might get brave at some point and try to improve some stuff. cheers, Tony _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Bugs ? Startlazarus increases link times
Tested linking times (not including compiling time) Lazarus: - lazarus.new.exe 2 minutes : 37 seconds StartLazarus - lazarus.new.exe 2 minutes : 54 seconds Celeron 400mhz, 327MB RAM, Windows 2000 Lazarus Version: 0.9.7 RB Alpha LD.exe version: not sure, it is 279,552B in size Maybe some people can try on Lazarus 0.9.8 and later, and of course on other platforms. I just use a chronograph on a stopwatch. I recommend turing off clean all and only building the IDE itself, if you are going to be doing this. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Bugs ? Startlazarus increases link times
Ok some stats from my setup then: Lazarus version: Subversion checkout on saturday (same happened with 0.9.8 however) CPU: AMD Sempron 2800+ CPU Mhz: 1600 Acer Aspire 3000 ld version - from binutils 2.15.92.0.2 *cast confusion. on . A.J. On Tuesday 30 August 2005 20:01, L505 wrote: Tested linking times (not including compiling time) Lazarus: - lazarus.new.exe 2 minutes : 37 seconds StartLazarus - lazarus.new.exe 2 minutes : 54 seconds Celeron 400mhz, 327MB RAM, Windows 2000 Lazarus Version: 0.9.7 RB Alpha LD.exe version: not sure, it is 279,552B in size -- A.J. Venter Chief Software Architect OpenLab International http://www.getopenlab.com http://www.silentcoder.co.za _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
It whould be, but I think not a lot of people have tried to do this yet. (Me neither, btw). What commandline options does FP hand to fpc to compile it, and what is the difference to the commandline lazarus generates ? fp has a compiled in compiler. I noticed this, because whenever I upgrade just my compiler.. the old compiler is still used when I fire up FP IDE. This is very important for people to know :) Could cause headaches, so please people, pay attention. i.e. you must rebuild the FP IDE if you want to upgrade your compiler in text mode development, AFAICT _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] making WIN32 DLL ?
They can. Only real DOS apps cannot. On windows a console app can be a real Win32 app, and can hence load libraries. Dos apps running in a Command-line windows usually cannot load libraries. Michael. thx. And I just assume linux/unix has had DSO's for a long long time in command line mode, so no worries there. Way before those they just used pipes, from what I remember reading. But not sure the exact dates and timelines. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Bugs ? Startlazarus increases link times
Anyone know how can I find out my LD version if I just have the executable handy? I don't see it in the |properties|summary|version| ld --version _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Bugs ? Startlazarus increases link times
L505 wrote: ld version - from binutils 2.15.92.0.2 *cast confusion. on . A.J. Anyone know how can I find out my LD version if I just have the executable handy? I don't see it in the |properties|summary|version| _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives usually from a commandline you type: ld --version _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus / C++ Application Released
On Tuesday 30 August 2005 10:10, Razvan Adrian Bogdan wrote: On 8/30/05, Razvan Adrian Bogdan [EMAIL PROTECTED] wrote: On 8/29/05, Chris Gordon-Smith [EMAIL PROTECTED] wrote: Hullo All This is to announce the release of version 0.2 of my SimSoup Artificial Chemistry simulator program. As far as I am aware, this is the first program that combines use of the Lazarus Component Library (LCL) for the presentation of the user interface with C++ for other program logic. The integration of C++ with Lazarus / FPC provides a programming environment similar to that of C++ Builder (version 0.1 of the program was developed with C++ Builder). For screenshots see:- http://www.simsoup.info/SimSoup_Screenshot.html I will welcome any feedback at the email address mentioned on my Home page (see below). How did you call the C++ code from FPC or did you do only from C++ to FPC ? Opps i just saw on your website, verry nice project. Razvan Thanks. I have sent some basic information on the approach separately in a response to Michael Van Canneyt's email. Please note that the information currently on the website is rather old. It shows some of the low level techniques, but I'll need to update it in due course. -- Chris Gordon-Smith London http://www.simsoup.info _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Looks like GMane news relay is on line again
After they resubscribed to the lazarus list the newsgroup at gmane for lazarus seems to be working again. I am posting this in order to verify that it passes through. The server is: news.gmane.org and the NG is: gmane.comp.ide.lazarus.general /Bo Bo Berglund _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] SVN Updates Initial LCL - Carbon interface
Marc Weustink wrote: Hi r7586: I'm proud to announce the initial steps of the carbon interface. The Hello world example compiles and runs (*). The interface is far form complete, on basic Form and Button support is available. Now with screenshot: http://www.dommelstein.net/scrap/carbon_hello.png Marc _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
RE: [lazarus] Application crash
Vincent Snijders wrote: What about using the gdb that comes with lazarus (on windows)? See for the path: Environment, Debugger Options, General Tab. The default is: c:\lazarus\mingw\bin\gdb.exe Thanks! I didn't know about that. You saved me from lots of fumbling there. :) I guess the Wiki docs needs updating on this. I'll do it. Prognatus. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
RE: [lazarus] Application crash
Vincent Snijders wrote: Try creating a back trace, it gives us some information where it went wrong OK, here's the output: Starting program: D:\My Documents\$Project\!willy/willy.exe Program received signal SIGSEGV, Segmentation fault. 0x7c918fea in ntdll!RtlpWaitForCriticalSection () from ntdll.dll (gdb) bt #0 0x7c918fea in ntdll!RtlpWaitForCriticalSection () from ntdll.dll #1 0x0002 in ?? () #2 0x0006e870 in ?? () (gdb) quit Are there debugging info missing in the exe file? Prognatus. smime.p7s Description: S/MIME cryptographic signature
RE: [lazarus] Application crash
Hmmm... I'm wondering if it's a path issue? Maybe related to long paths, paths on other disks than Lazarus, or similar. See also this: http://www.lazarus.freepascal.org/mantis/view.php?id=900 - Bjørn. --- _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Application crash
Try installing lazarus on a directory that does not have spaces on it's name (the best is a short directory name). I would say this is a bug with long file names on the interface. Don't worry. Programs produced by lazarus do not have this bug ;-) -- Felipe Monteiro de Carvalho
RE: [lazarus] Application crash
Felipe Monteiro de Carvalho wrote: Try installing lazarus on a directory that does not have spaces on it's name (the best is a short directory name). I would say this is a bug with long file names on the interface. I did. It's installed in c:\lazarus\ Only my project is located elsewhere. Prognatus. smime.p7s Description: S/MIME cryptographic signature
