will lazarus Win32 IDE project files ex. lpr lpi work with lazarus win64 lazarus / 34-Windows ---------------------------------------------------------------------- picstart · 2012-09-22 13:38 I have had unpleasant past experiences with the dependencies and hidden( not obvious) file placement in the IDE. Like dependencies on users\,,\\\\\ for source and compilation. I will be building a new PC using win64. so the user will be different. If the lazarus folder including all the source code for components and user projects from the win32 PC are restored on the new 64bit machine and lazarus 64 installed does it have any chance of working? Will the IDE find the packages and rebuild ? Will the user forms and *pas files be found or do all the dependencies built into the lpi lpr files have to be dugout?  I expect the *.pas files will have a chance of working but I hope to avoid reentering ( reproducing) all the forms. Is there is a way to confine all the lazarus IDE dependencies to just the  lazarus folder and avoid the unpleasantness going forward? ---------------------------------------------------------------------- Leledumbo · 2012-09-22 13:54 QuoteLike dependencies on users\,,\\\\\ for source and compilationThere should never be one, otherwise I can't compile my projects on both windows and linux without problems. QuoteIf the lazarus folder including all the source code for components and user projects from the win32 PC are restored on the new 64bit machine and lazarus 64 installed does it have any chance of working?Lazarus uses single directory structure for ALL platforms, so it should work as long as you don't use platform specific packages. QuoteWill the IDE find the packages and rebuild ?Normally (they will be listed in the package manager), but you still have to tell the IDE to install them. QuoteWill the user forms and *pas files be found or do all the dependencies built into the lpi lpr files have to be dugout?  I expect the *.pas files will have a chance of working but I hope to avoid reentering ( reproducing) all the forms.Project files should be OK, unless there's a hardcoded path (e.g. C:\blabla) somewhere. QuoteIs there is a way to confine all the lazarus IDE dependencies to just the  lazarus folder and avoid the unpleasantness going forward?Depending on the "dependencies". If you mean packages, and they're located somewhere outside the IDE folder, then it's unlikely. The IDE might save the path as absolute instead of relative and that could be a problem. ---------------------------------------------------------------------- picstart · 2012-09-23 18:14 Thanks for the heads up. Looks like there is a viable path between laz 32 on win 32 to win 64 with laz 64 that doesn't require re-inputting all the forms.  I'm still nervous about the users directory and lazarus dependencies. Every time there was a major release of lazarus I would just pre-emptively delete everything in users referencing lazarus and things would be run reliably. Not to do so often caused issues. Is there is a way to change the default state of  lazarus automatically creating dependencies on the widows users directory? ---------------------------------------------------------------------- Leledumbo · 2012-09-24 00:41 QuoteIs there is a way to change the default state of  lazarus automatically creating dependencies on the widows users directory?What dependencies? If what you mean is the IDE settings (and thus, not related to any projects) use --primary-config-path= command line option. ---------------------------------------------------------------------- picstart · 2012-09-24 17:44 The unpleasant dependencies arise from stuff going into users\xxxx\Appdata\local\lazarus. This has the consequence that the lazarus folder is incomplete and doesn't represent the full state of a lazarus system. It would be good news if lazarus could be fully contained within a single folder. It's not a big deal I just delete the users\xxxx\Appdata\local\lazarus unpleasantness prior to a rebuild the lazarus IDE. Is there a way to not have the lazarus IDE use users\xxxx\Appdata\local\lazarus for storing info? ---------------------------------------------------------------------- Leledumbo · 2012-09-25 16:20 I see, so you're really talking about Lazarus itself. As I said, you can use --primary-config-path or -pcp for short to force lazarus search for its configuration files in the given directory. Modify your shortcut to always call lazarus using this option. Note that Lazarus can't put its configuration in its own folder due to Unix system concept of application directory.