Odd project error message behaviour

[petevick]

I'm working on a project with a mate in Oz, I'm in the UK, we send the same project folder backwards and forwards so it's always the same project. When I get an error in the project it usually gives the line number and a clue to what's causing the error, when my mate gets an error all he gets a "Fatal: (1018) Compilation aborted" message. We've checked his Tools>Options for any debug options and they seem to match my settings. Presumably the project options will be the same as we are using the same project folder, or are project options written elsewhere ??

[wp]

Just an idea: Do not copy the project.lps file (or delete it before you open the project received from your friend). The lps file is the "session" file and contains a lot of settings specific for the computer used. I could imagine that when a session file is used by another computer there could be issues.

[marcov]

Also, click right on a line in the error message and make sure that all filtering is off.

Sometimes a linker error that it is missing some library is hidden.

[MarkMLl]

Just an idea: Do not copy the project.lps file (or delete it before you open the project received from your friend). The lps file is the "session" file and contains a lot of settings specific for the computer used. I could imagine that when a session file is used by another computer there could be issues.

Also potentially  exclude .res, that was raised recently where somebody was doing multiple concurrent builds and found clashing .res files being put into the same directory.

You need .lpi, .lpr, .pas, .lfm and (if the project group addon is installed) .lpg. Possibly also .inc, but be careful if any of those are built using external tools (e.g. I use them to embed FPC and project revision versions).

MarkMLl

[petevick]

@ wp - thanks, we'll give that a go

@ marcov - thanks, we've already checked that, all good.

@ MarkMLI - thanks, we'll try that as well.

[Josh]

Hi

Are you using the exact same version of laz and fpc OS and CPU?
edit: make sure you both are using the exact sameversions of any components(inbuilt and/or 3rd party)

if not you could try setting the option maximum compatibility in project options.

If you have multiple builds for different OS, it best to make sure that you set the build to the machine your sharing it too.I have issues if i dev on windows and then move project to mac, mac has a major fit, i have to go back to windows set build for mac; save it thenmove back to mac to open it..

Also do not include the lib folder with in your project folder when sharing.. That way all units will be recompiled for target.

just some ideas

[petevick]

Hi

Are you using the exact same version of laz and fpc OS and CPU?
if not you could try setting the option maximum compatibility in project options.

If you have multiple builds for different OS, it best to make sure that you set the build to the machine your sharing it too.I have issues if i dev on windows and then move project to mac, mac has a major fit, i have to go back to windows set build for mac; save it thenmove back to mac to open it..

Also do not include the lib folder with in your project folder when sharing..

just some ideas

Thanks Josh. We'll look into that. Regarding the lib folder, I already exclude that.

[VisualLab]

Interesting problem. This makes me wonder, because I quite often had (and still do) encounter the situation of projects developed on two machines. In my case it looks like this:

• computer at work: Windows 8 64-bit, Lazarus 3.2,
• computer at home: Windows 10 64-bit, Lazarus 3.0, recently upgraded to 3.4.

I am moving the entire directory with the source files, but without the subdirectories with the compiled and backup files (lib, backup). So there are files in it: pas, lfm, lpi, lps, res, ico. And it all compiles without crashes or errors. In most cases, these were quite simple programs: a main window, a few dialog windows, a few data processing modules. Mostly used classes, both library and own (but not installed in Lazarus). In most cases, the settings for such a development program are stored in an INI file.

So maybe in your case there are some differences in Lazarus? For example, specific packages installed? Any specific settings in the OS?

[petevick]

Also, click right on a line in the error message and make sure that all filtering is off.

Sometimes a linker error that it is missing some library is hidden.

turns out it was this after all, even though he had exactly the same settings as me, changing from Filter non urgent Messages>Filter Verbose Messages and below to Filter non urgent Messages>Filter Debug Messages and below fixed his problem. Thanks again