Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, 30 Dec 2011 05:03:23 +0100 Hans-Peter Diettrich drdiettri...@aol.com wrote: Marco van de Voort schrieb: As part of the 2.6.0 documentation effort, I regenerated the docs for FPC, and as usual I also try to build the LCL docs. I had to create some XMLs for non existing LCL units. [...] Since it's so overly complicated to interface such an application with the existing FPDoc tools (fpdoc, makeskel...), the next version will be much closer to Lazarus packages, using heavily modified versions of the fpc/utils/fpdoc/ units. The final project will become available in lazarus examples/docmgr (not to confuse with dockmanager, for use by everybody :-) [Recommendations for better directory/project names are welcome :-] It seems closely related to fpdoc, so maybe examples/fpdocmgr [...] I also noticed some copies of the RTl docs in docs/xml/rtl but these don't seem to be diffs/additions but full copies (and now it is hard to find out what these actually change). Can these be removed? Dunno, I also wonder when this (Unicode strings) change will be really finished :-( What does that mean? According to svn you added the files. Are they still needed or can they be removed? Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Loaded Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Notification IMO the LDock... stuff is so outdated, that it should be removed from the repository. I removed them. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, 30 Dec 2011 05:22:12 +0100 Hans-Peter Diettrich drdiettri...@aol.com wrote: Mattias Gaertner schrieb: All three should get their own docs. LCL+LCLBase can be bundled. ACK I also noticed some copies of the RTl docs in docs/xml/rtl but these don't seem to be diffs/additions but full copies (and now it is hard to find out what these actually change). Can these be removed? DoDi? These old copies can be removed. Ok. I removed them. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Mattias Gaertner schrieb: [Recommendations for better directory/project names are welcome :-] It seems closely related to fpdoc, so maybe examples/fpdocmgr Fine, this will become the name of version 2.0 :-) [...] I also noticed some copies of the RTl docs in docs/xml/rtl but these don't seem to be diffs/additions but full copies (and now it is hard to find out what these actually change). Can these be removed? Dunno, I also wonder when this (Unicode strings) change will be really finished :-( What does that mean? Sorry, I missed the target. My comment was aimed at the recent LazUtils and stringhandling changes. Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Loaded Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Notification IMO the LDock... stuff is so outdated, that it should be removed from the repository. I removed them. Here outdated means the source code, not the documentation. Not only the LDock manager was never finished, docking on Windows is broken since almost a year, and according bug reports and patches have been delayed AFAIR to Lazarus 1.0 - what means to me that they will not be fixed this century :-( DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Mattias Gaertner schrieb: Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Loaded Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Notification IMO the LDock... stuff is so outdated, that it should be removed from the repository. I removed them. Please also remove it from the LCL(Base?) source package. Currently rebuilding the LCL fails with missing unit LDockTree in alllclunits :-( As a workaround I added a dummy lcl\ldocktree.pp, to make the compiler happy. DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, 30 Dec 2011 12:33:58 +0100 Hans-Peter Diettrich drdiettri...@aol.com wrote: Mattias Gaertner schrieb: Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Loaded Warning: Target ID of link in unit LDockCtrl is unknown: #rtl.Classes.TComponent.Notification IMO the LDock... stuff is so outdated, that it should be removed from the repository. I removed them. Please also remove it from the LCL(Base?) source package. Currently rebuilding the LCL fails with missing unit LDockTree in alllclunits :-( Sorry. Done. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Marco van de Voort schrieb: lazutils is now a separate package, and lcl references the new lazutils package. Everything is done and committed, in theory generating CHMs is a matter of installing dependencies, and then running fixdocs.sh in the fpcdocs repo and then running build_html_chm.sh in lazarus/docs/html These scripts may be nice, but are not very useful for Window users. That's why my documentation manager tries to import LPK files, and now I ran into a problem with the new LazUtils.lpk: How can $(IDEBuildOptions) be evaluated in code? This macro seems to specify compiler options (-Fi, -Fu...), which also are required by the fpdoc source parser. For the RTL and FCL documentation the fpcdocs Makefile can be used on every platform, to produce the fully expanded fpdoc and makeskel commandlines, which can be redirected into an file and parsed by the docmgr. But how get the actual commandlines or compiler options for Lazarus packages? DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Custom OS/CPU targets for FPC - build help
Hi, as I'm unable to sign-up on Lazarus forums (as control question 1+2= rejects answer 3) the question is placed here. Free Pascal Compiler version 2.7.1 [2011/12/25] for x86_64 Copyright (c) 1993-2011 by Florian Klaempfl and others c:\Lazarus\fpc\2.7.1\bin\x86_64-win64\ppcx64.exe [options] inputfile [options] ... -Tx Target operating system: -Tdarwin Darwin/Mac OS X -TlinuxLinux -Twin64Win64 (64 bit Windows systems) As you can see, three operating system targets are currently supported by installed freepascal compiler. What commands do I have to use to rebuild FPC another target OS/CPU like Win32/i386 will be supported ? Thx. David -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, 30 Dec 2011 13:52:34 +0100 Hans-Peter Diettrich drdiettri...@aol.com wrote: Marco van de Voort schrieb: lazutils is now a separate package, and lcl references the new lazutils package. Everything is done and committed, in theory generating CHMs is a matter of installing dependencies, and then running fixdocs.sh in the fpcdocs repo and then running build_html_chm.sh in lazarus/docs/html These scripts may be nice, but are not very useful for Window users. That's why my documentation manager tries to import LPK files, and now I ran into a problem with the new LazUtils.lpk: How can $(IDEBuildOptions) be evaluated in code? This macro seems to specify compiler options (-Fi, -Fu...), which also are required by the fpdoc source parser. The macro IDEBuildOptions are only the custom options set by the user. For the RTL and FCL documentation the fpcdocs Makefile can be used on every platform, to produce the fully expanded fpdoc and makeskel commandlines, which can be redirected into an file and parsed by the docmgr. But how get the actual commandlines or compiler options for Lazarus packages? You can read the .compiled file or the Makefile.compiled or run the tool as IDE plugin. As IDE plugin you get all macros. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, Dec 30, 2011 at 05:03:23AM +0100, Hans-Peter Diettrich wrote: Marco van de Voort schrieb: As part of the 2.6.0 documentation effort, I regenerated the docs for FPC, and as usual I also try to build the LCL docs. I had to create some XMLs for non existing LCL units. You're busy with Lazarus these days, too? :-) I do doc work from time to time. And when I update FPC docs, I test the state of Lazarus too (and usually they are broken :-) I've just finished a first version of an documentation manager, which can create documentation projects for RTL, FCL, and any Lazarus packages. Main usage: quick creation of the final documentation, unit skeletons and update of existing XML doc files. For user documentation or for the lazarus project? Those are not necessarily the same things. Since it's so overly complicated to interface such an application with the existing FPDoc tools (fpdoc, makeskel...), the next version will be much closer to Lazarus packages, using heavily modified versions of the fpc/utils/fpdoc/ units. The final project will become available in lazarus examples/docmgr (not to confuse with dockmanager, for use by everybody :-) [Recommendations for better directory/project names are welcome :-] I think lowering the reliance on makefiles and shellscripts is a good thing. I'm already thinking about fixing the lpr in docs/html in time. But I first have to figure out if it is functional or not. If only because I'm slowly reaching the borders of my shellscript knowledge. But while I like that direction, currently for me it is more important to keep the lcl building lazarus free. (that is no need for a updated build updated lazarus to build the docs, since I do it remotely on a server) I also commited a clenaed up version of the script I use to generate lcl.chm as docs/html/build_lcl_chm.sh. The documentation manager will eliminate the need for any scripts, in an platform independent way :-) If that is at the expense of requiring a GUI system then IMHO it gets worse rather than better:-) What is the plan with this package? Is it a part of the LCL or really an optional component? The LCL docs refers to lazutf8 81 times. If it is just a matter of generating an extra CHM and set up the buildscripts for it, just say so and I'll do it. Perhaps the LazUtils (etc.) documentation should be added to the LCL package, like the LCLBase documentation is (the essential) part of that package. Note: documentation packages must not necessarily equal Lazarus (source) packages! I agree with that. OTOH the split has been done, and it is now easier to maintain it than to undo it. But let's keep it in mind for the next reorganization. I also noticed some copies of the RTl docs in docs/xml/rtl but these don't seem to be diffs/additions but full copies (and now it is hard to find out what these actually change). Can these be removed? Dunno, I also wonder when this (Unicode strings) change will be really finished :-( I don't know what that has to do with it. Current docs describe the 2.6 branch not the 2.7 branch which has unicodestrings. But these files are already unmaintained from before the 2.6 branch existed, so I don't know what they are for. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On 30.12.2011 16:23, Marco van de Voort wrote: Dunno, I also wonder when this (Unicode strings) change will be really finished :-( I don't know what that has to do with it. Current docs describe the 2.6 branch not the 2.7 branch which has unicodestrings. But these files are already unmaintained from before the 2.6 branch existed, so I don't know what they are for. They are code page aware strings, not unicodestrings. :) That are two different string types and the latter existed already in 2.4 and maybe earlier ;) Regards, Sven -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] trunk OSX Lion 10.7.2 Scrolling Problem
On OSX lion 10.7.2 in lazarus trunk, the svn revision 33972 breaks the mouse wheel scrolling in the ide editor (at least for a magic mouse) - The view stutters, does not scroll, or scrolls only some lines and stops. The version before worked fine. In synedit.pp the following hack brings back normal scrolling behaviour: Tested on svn 34518. -- procedure TCustomSynEdit.WMMouseWheel(var Message: TLMMouseEvent); begin Message.Result:=0; end; -- Helmut -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] trunk OSX Lion 10.7.2 Scrolling Problem
Seems that Mac sends a delta of 40 per click, win and linux do 120 you can change this in synedit until fixed procedure TCustomSynEdit.WMMouseWheel(var Message: TLMMouseEvent); var lState: TShiftState; const WHEEL_DELTA = 120; begin Note you may have similar issues in other windows (e.g. disassembler) On 30/12/2011 16:51, Helmut Hartl wrote: On OSX lion 10.7.2 in lazarus trunk, the svn revision 33972 breaks the mouse wheel scrolling in the ide editor (at least for a magic mouse) - The view stutters, does not scroll, or scrolls only some lines and stops. The version before worked fine. In synedit.pp the following hack brings back normal scrolling behaviour: Tested on svn 34518. -- procedure TCustomSynEdit.WMMouseWheel(var Message: TLMMouseEvent); begin Message.Result:=0; end; -- Helmut -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] trunk OSX Lion 10.7.2 Scrolling Problem
On Friday 30 of December 2011 18:22:11 Martin wrote: Seems that Mac sends a delta of 40 per click, win and linux do 120 Not only Mac (carbon cocoa) ,but qt under mac too. zeljko you can change this in synedit until fixed procedure TCustomSynEdit.WMMouseWheel(var Message: TLMMouseEvent); var lState: TShiftState; const WHEEL_DELTA = 120; begin Note you may have similar issues in other windows (e.g. disassembler) On 30/12/2011 16:51, Helmut Hartl wrote: On OSX lion 10.7.2 in lazarus trunk, the svn revision 33972 breaks the mouse wheel scrolling in the ide editor (at least for a magic mouse) - The view stutters, does not scroll, or scrolls only some lines and stops. The version before worked fine. In synedit.pp the following hack brings back normal scrolling behaviour: Tested on svn 34518. Helmut -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Lazarus Logo
Hi all and Happy Holidays, I'm going to complete the develop of my program and I would insert a Lazarus' Hi-Res logo on the splashscreen, while loading. But I can't find anything bigger (or equal) to 200x200 pixel. Could you help me? Best Regards, Kjow -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Marco van de Voort schrieb: On Fri, Dec 30, 2011 at 05:03:23AM +0100, Hans-Peter Diettrich wrote: I've just finished a first version of an documentation manager, which can create documentation projects for RTL, FCL, and any Lazarus packages. Main usage: quick creation of the final documentation, unit skeletons and update of existing XML doc files. For user documentation or for the lazarus project? Those are not necessarily the same things. For documentation writers, and for users which want to have their local or otherwise specialized (national...) documentation. Since it's so overly complicated to interface such an application with the existing FPDoc tools (fpdoc, makeskel...), the next version will be much closer to Lazarus packages, using heavily modified versions of the fpc/utils/fpdoc/ units. The final project will become available in lazarus examples/docmgr (not to confuse with dockmanager, for use by everybody :-) [Recommendations for better directory/project names are welcome :-] I think lowering the reliance on makefiles and shellscripts is a good thing. I'm already thinking about fixing the lpr in docs/html in time. But I first have to figure out if it is functional or not. If only because I'm slowly reaching the borders of my shellscript knowledge. I don't understand why (platform specific) shell scripts shall be used for documentation purposes - is Pascal not suited for such tasks? ;-) But while I like that direction, currently for me it is more important to keep the lcl building lazarus free. (that is no need for a updated build updated lazarus to build the docs, since I do it remotely on a server) Building final documentation is not a special problem when project files are used, which can be generated and updated by e.g. my documentation manager - then FPDoc can do it all. I also commited a clenaed up version of the script I use to generate lcl.chm as docs/html/build_lcl_chm.sh. The documentation manager will eliminate the need for any scripts, in an platform independent way :-) If that is at the expense of requiring a GUI system then IMHO it gets worse rather than better:-) A GUI is not a requirement, it only simplifies the development of the desired functionality :-) I consider to commit a first demo version of my documentation manager, to clarify how it looks and what it can do. Then everybody can see what parts can be made available in a commandline version, too. DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Sven Barth schrieb: On 30.12.2011 16:23, Marco van de Voort wrote: Dunno, I also wonder when this (Unicode strings) change will be really finished :-( I don't know what that has to do with it. Current docs describe the 2.6 branch not the 2.7 branch which has unicodestrings. But these files are already unmaintained from before the 2.6 branch existed, so I don't know what they are for. They are code page aware strings, not unicodestrings. :) That are two different string types and the latter existed already in 2.4 and maybe earlier ;) I wonder how strings with different encoding will work together, without kind of Unicode strings - be UTF-8 or UTF-16. I also wonder what's the benefit of using strings with different encodings together, when every other string operation will require a codepage translation... DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
Mattias Gaertner schrieb: For the RTL and FCL documentation the fpcdocs Makefile can be used on every platform, to produce the fully expanded fpdoc and makeskel commandlines, which can be redirected into an file and parsed by the docmgr. But how get the actual commandlines or compiler options for Lazarus packages? You can read the .compiled file or the Makefile.compiled or run the tool as IDE plugin. As IDE plugin you get all macros. It looks like the LCL compilation depends on the used widgetset? Which version of LCL.compiled should be used, to obtain meaningful compiler options for creating documentation? DoDi -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Logo
Dear Kjow: i am using a running cheetah. If you want, i can pass to you the routines. yours, Ing. Héctor F. Fiandor Rosario hfian...@infomed.sld.cu -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas Infomed: http://www.sld.cu/ -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Custom OS/CPU targets for FPC - build help
What commands do I have to use to rebuild FPC another target OS/CPU like Win32/i386 will be supported ? http://wiki.lazarus.freepascal.org/Cross_compiling -- View this message in context: http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Custom-OS-CPU-targets-for-FPC-build-help-tp3621041p3621677.html Sent from the Free Pascal - Lazarus mailing list archive at Nabble.com. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Documentation update (CHM building, lazutils)
On Fri, 30 Dec 2011 19:40:00 +0100 Hans-Peter Diettrich drdiettri...@aol.com wrote: Mattias Gaertner schrieb: For the RTL and FCL documentation the fpcdocs Makefile can be used on every platform, to produce the fully expanded fpdoc and makeskel commandlines, which can be redirected into an file and parsed by the docmgr. But how get the actual commandlines or compiler options for Lazarus packages? You can read the .compiled file or the Makefile.compiled or run the tool as IDE plugin. As IDE plugin you get all macros. It looks like the LCL compilation depends on the used widgetset? Which version of LCL.compiled should be used, to obtain meaningful compiler options for creating documentation? For the units in the LCLBase see lcl/Makefile.compiled. For units in the LCL interfaces use the lcl/interfaces/*/Makefile.compiled. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Logo
2011/12/30 Ing. Héctor F. Fiandor Rosario hfian...@infomed.sld.cu: Dear Kjow: i am using a running cheetah. If you want, i can pass to you the routines. yours, Ing. Héctor F. Fiandor Rosario hfian...@infomed.sld.cu Thank you, I can evaluate. But I would something like official logos: the stylized cheetah (the IDE icon) or the cheetah footprint, both with the Lazarus word. Best Regards, Kjow -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Logo
2011/12/30 Kjow antispamm...@gmail.com: Hi all and Happy Holidays, I'm going to complete the develop of my program and I would insert a Lazarus' Hi-Res logo on the splashscreen, while loading. But I can't find anything bigger (or equal) to 200x200 pixel. Could you help me? Maybe you can use: http://svn.freepascal.org/svn/lazarus/trunk/images/powered-by.svg Vincent -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Tip - Getting geolocation with Free Pascal
Hello, For a year, I have been developing some utilities for the desktop and the web programming. The name of this project is LazSolutions and it includes mailing, compression, encriptation, interpreter for arithmetic expressions, demo builders with time limitations and several other features. Recently, I have implemented some routines for geolocation (using MaxMind database). With only two functions, supplying a valid IP, we can get information about the related country and the city. Here, find The picture of the running demo: http://imagebin.org/191006 From SVN, you can get your copy of it: https://lazsolutions.googlecode.com/svn, open and run the demo lazsolutions\trunk\Demos\LSGeoIP. I invite all to test and use this feature. What do you think if only with two coordenates, we could create an image showing the map of the place? The demo does exactly it. By means of a supplied IP, we can call a function and look for the map using Google APIs. It's a very good toy to play! Happy New Year, Enjoy! -- Silvio Clécio Site - silvioprog.com.br LazSolutions - code.google.com/p/lazsolutions -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Logo
2011/12/30 Vincent Snijders vincent.snijd...@gmail.com: Maybe you can use: http://svn.freepascal.org/svn/lazarus/trunk/images/powered-by.svg Vincent Nice, SVG! Thank you! Is there SVG of IDE icon (the stylized cheetah)? Best Regards Kjow -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] MFC42D.DLL Used by Lazarus or FPC?
I have been working on a Lazarus program that as of today reports that it can't find MFC42D.DLL. Can anyone tell me if Lazarus uses this dll? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] MFC42D.DLL Used by Lazarus or FPC?
On Fri, Dec 30, 2011 at 05:02:50PM -0600, Curt Carpenter wrote: I have been working on a Lazarus program that as of today reports that it can't find MFC42D.DLL. Can anyone tell me if Lazarus uses this dll? In general lazarus doesn't, so something else must link it in. In decreasing probability: - a library that you use directly. - a library that one of the external components you use use. - a library that one of Lazarus components or lazarus CCR components use (maybe richedit) -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
