SVN Release lazarus-0.9.30-fpc-2.4.2-win32 is quirky lazarus / 11-Options ---------------------------------------------------------------------- picstart · 2011-03-26 17:08 The prospect of adding any new package to lazarus or an update is unpleasant. Now in fairness hello world did work this time. But only after deleting all the dependencies in  Documents and  settings\userxxx\local settings\Application Data\lazarus ( I find little value in this dependency since most often it has to be wiped out to restore confidence in an update situation)  Adding packages is another thing Ex I added sqlite and the static nature of lazarus means your heart is in your mouth since all must recompile to have a working system (Delphi avoided this)  Lazarus this time it actually did recompile but it will not run because it couldn't find a compatible sqlite.dll. I added both the sqlite and the sqllit3 packages. I had expected a delete of the  Documents and  settings\userxxx\local settings\Application Data\lazarus and a reinstall of 29.30 fpc 2.4.2 win32 to Xppro would get me back to square one and that I could start weeding out the mess. Some how there is another dependency or more that retains knowledge of adding the sqllite package and I can't run the lazarus IDE due to sqlite.dll not being compatible ( can't find sqlite changes section in the dll) I know there are work arounds like going back to an old lazarus.exe.With increasing and fatal dependencies on this file or the other would it be a good idea to have at least all files in one folder called lazarus. I actually like lazarus But I feel I'm riding a leopard (cheetah) that wants to bite me. ---------------------------------------------------------------------- laguna · 2011-03-26 18:11 copy sqlite.dll in c:/lazarus rebuild lazarus with include package sqlite ---------------------------------------------------------------------- picstart · 2011-03-26 19:27 I already had tried adding sqllite.dll to the lazarus directory ..With the sqlite package added lazarus expects a specific version of sqlite.dll and it was not the one I have. Sure I can get the right one but having the wrong sqlitedll version shouldn't stop the lazarus IDE. The workaround of going to lazarus_old.exe unravels it for me. The point is that the lazarus IDE is highly dependent on every other part of lazarus and some parts are held in other structures Documents and settings\user..... which luckily so far can be deleted ( often must be deleted) to assure a good install. Lazarus does work I'm a fan yet I'm just concerned as the files proliferate and the system boats to kilofiles this single point of failure issue may become a major issue. I use Xilinx FPGA software they are in the kilofile never never land already. An application that needs  ten thousand files to work is a monstrosity. ---------------------------------------------------------------------- JD · 2011-03-26 20:17 I agree that Lazarus can be quirky. I dumped the version with fpc 2.4.2 for a version with fpc 2.4.3 because of problems similar to what you described here. Quote from: picstart on March 26, 2011, 08:27:07 pm An application that needs  ten thousand files to work is a monstrosity. This is the case for practically ALL development tools. Name it - C/C++, Java, Delphi etc. They all rely on thousands of classes/routines in many, many files - some of them interdependent. I don't expect it to go away. ---------------------------------------------------------------------- TurboRascal · 2011-03-27 12:42 @picstart, I understand that encountering problems frustrates you, but there is no need to turn your frustration to hostility towards Lazarus. Problems you describe are not errors, but your lack of understanding how Lazarus works. Just read the documentation, and if you don't find the answer, ask here; and stay cool! NHF. Now, to the technical matters, Lazarus obviously must have all dependency dlls available. Rather than guessing where you need to put them (say, lazarus directory as suggested, then putting the same dll to your app's directory), you should put the dlls to a directory in %PATH%. You could just cram them to the SYSTEM32 directory, but that's not such a good idea, better create another dir and include it to %PATH%, and every app will get it. The dll's you need now are sqlite.dll (for the sqlite package) you already got, and sqlite3.dll (for the sqlite 3 package). The minor versions are mostly irrelevant! If you make sure those two dlls are in path, Lazarus WILL work fine, and also your apps. Don't forget to distribute sqlite dlls you used with your apps! ---------------------------------------------------------------------- lainz · 2011-03-27 15:07 Quote from: TurboRascal on March 27, 2011, 02:42:27 pm@picstart, I understand that encountering problems frustrates you, but there is no need to turn your frustration to hostility towards Lazarus. Problems you describe are not errors, but your lack of understanding how Lazarus works. Just read the documentation, and if you don't find the answer, ask here; and stay cool! NHF. Now, to the technical matters, Lazarus obviously must have all dependency dlls available. Rather than guessing where you need to put them (say, lazarus directory as suggested, then putting the same dll to your app's directory), you should put the dlls to a directory in %PATH%. You could just cram them to the SYSTEM32 directory, but that's not such a good idea, better create another dir and include it to %PATH%, and every app will get it. The dll's you need now are sqlite.dll (for the sqlite package) you already got, and sqlite3.dll (for the sqlite 3 package). The minor versions are mostly irrelevant! If you make sure those two dlls are in path, Lazarus WILL work fine, and also your apps. Don't forget to distribute sqlite dlls you used with your apps! you know how I can use both Lazarus SVN and Lazarus 0.9.30? The problem I have is settings are stored in the same folder C:\Users\$username$\AppData\Local\Lazarus and the directories where I have each version are different, so when I configure settings for SVN the release doesn't works and vice-versa. How I can set the settings directory separated for each version? ---------------------------------------------------------------------- vvzh · 2011-03-27 15:57 http://wiki.freepascal.org/Multiple_Lazarus ---------------------------------------------------------------------- picstart · 2011-03-27 16:11 QuoteI understand that encountering problems frustrates you, but there is no need to turn your frustration to hostility towards Lazarus.First I am a fan of Lazarus and yes I said that already in an earlier post. I can and did work around the dll issue. I am reasonably familiar with the paths. The point which I had hoped to make is that these issues seem to leap out when a new update is installed ( quirkiness). This means work around knowledge is mission critical. Sure some will describe work arounds as simply knowledge of the system often ignoring the fact that something happened that needed fixing. Complexity enhances the probability of failure. Thousands of inter dependencies even if each one has a low probability of failure means success is at much risk since  it is the geometric sum. No one would fly if it only was safe when every single piece of the plane worked. Resiliency has value. If all comments are to be classified as hostile then most will assume the system is perfect. However if it is perfect then why are there updates? I understand a single bad dll can hold not onlythe Lazarus IDE hostage but even the OS. I can accept this as reality but never as good design. A resilient design would run the 99.9% of things that are good and drop the offending code. ---------------------------------------------------------------------- lainz · 2011-03-27 17:27 Quote from: vvzh on March 27, 2011, 05:57:21 pmhttp://wiki.freepascal.org/Multiple_Lazarus thankyou really easy I added this to Wiki: http://wiki.freepascal.org/Multiple_Lazarus#Windows ---------------------------------------------------------------------- TurboRascal · 2011-03-28 12:27 Quote from: picstart on March 27, 2011, 06:11:04 pm If all comments are to be classified as hostile then most will assume the system is perfect. However if it is perfect then why are there updates? I understand a single bad dll can hold not onlythe Lazarus IDE hostage but even the OS. I can accept this as reality but never as good design. A resilient design would run the 99.9% of things that are good and drop the offending code. Not all comments should be classified ones, but non-constructive ones are at risk of that The behavior you explained is not really a quirk, but a big issue concerning compiler architecture which won't simply be fixed by a regular update. I don't like it, I'd also prefer to get a message "cannot load library" and continue, but I've quickly learned to live with it until some day it is changed. For example, I am simply aware i shouldn't install sqlite 3 package before I get sqlite3 library (for example sqlite3.dll, but not sqlite.dll) and that's all; I don't quite feel I suffer greatly because of that. And now that you mentioned, most OS kernels today are monolithic too and a single module can crash the whole system. Good luck trying to complain, say microsoft about their OS Quote from: lainz on March 27, 2011, 07:27:16 pmI added this to Wiki: http://wiki.freepascal.org/Multiple_Lazarus#Windows Thank you for your contribution ---------------------------------------------------------------------- marcov · 2011-03-28 14:35 Quote from: picstart on March 27, 2011, 06:11:04 pmI understand a single bad dll can hold not onlythe Lazarus IDE hostage but even the OS. I can accept this as reality but never as good design. A resilient design would run the 99.9% of things that are good and drop the offending code. Well, Delphi doesn't solve this either. E.g. Zeos has the same problems under Delphi as Lazarus has, the client libs must be present, since the designcode uses it. More and more database pacakges do because of the live preview feature (seeing real data in the designer) Some of the various Delphi database systems didn't require it in the past, but that made live preview difficult, and required install of BDE/DBExpress and other standalone mediator packages that separately configure/register databases. (and I remember wrestling with BDE setup quite a bit over the years too) It's true that the situation of open source windows builds and their naming is highly variable and substandard, but that is not Lazarus' problem. People repeatedly point to packages as solution and the static linking of Lazarus as the problem, but I don't think this will solve anything. ---------------------------------------------------------------------- garlar27 · 2011-03-29 15:17 Well, the problems I had with sqlite where due to the library name under linux since they had a really weird (and useful when updating) name with version numbers on it.    It was a ... pain in the but. I solved it with a symlink (and a rename for windows).    Linux is more  ... "tricky" about that, and this is why I remember it. I don't remember if I had that problem on windows. And I also copied the dll file to the system or sys32 folder.