Why Lazarus is rebuilding project each time i run?

[hwnd]

Thanks. That made it a lot faster.

I was looking for such options in IDE settings. Now i know why i didn't find anything.

[hwnd]

Didnt want to create new thread.
Installed a Lazarus 1.1 with date of 2013-08-04 and with FPC 2.7.1.
This version because i need generics and stl.

And after creating new project and saving it and then running i always get error and it just stops:


Options changed, recompiling clean with -B
Failed to execute -B -MObjFPC -Scghi -O1 -g -gl -vewnhi -FiC:\Temp2\lib\i386-win32 -FuC:\Temp2\ -FUC:\Temp2\lib\i386-win32\ -l project1.lpr : 2


What it wants from me?

I can use commandline but why IDE fails each time i install 1.1?

[User137]

Just something to try:
- Tools -> Options: Environment -> Files. Check that all paths point to right places.
- Tools -> Rescan FPC source directory.
- Tools -> Build Lazarus with Profile: Clean Up + Build all.

[hwnd]

Tried all 3 options, still same.
Too bad, i wanted to make simple gui app with few buttons to test some algorithm for undo/redo with generics and stl.
But i guess i have to live with console app and command line compiling.

Dunno, if i point some working version of lazarus to fpc 2.7.x instead of "built in version" will it work?

Will install lazarus-1.0.10-fpc-2.6.2-win32 and try again.
Maybe even this will not work.

EDIT: Like expected, v1.0 with 2.6.x works fine.
So its a big bug in Lazarus

EDIT2

Downloaded fpc-2.7.1.i386-win32.zip, created folder called 2.7.1 and extracted all files to this folder. Executed Lazarus and pointed it to this folder. It said something about invalidf paths for make and one about fpc.cfg file is missing or something but i copied it over from 2.6.2 bin folder.
And it works. Lazarus is 1.0.10.
I dont know if this will work with 1.1 but atm im satisfied.
Decided to take the risk and try and to my suprise it compiles successfully.
Generics, stl etc, also available in GUI app.

Looks also much more stable.

Im happy.

[marcov]

In general, when getting strange internal errors that depend on order of compilation:

- reduce inline directives
- reduce unit import cycles.

Specially in combination with generics. This because both inline and generics somewhat live outside the normal "unit" system rules.

While these also matter for Delphi (though after XE that is somewhat reduced), these doubly go for FPC, which will try to inline generic methods in some cases, while Delphi doesn't even try as a rule.

[hwnd]

It didnt compile anything, even not the simplest console app or any demos.
Nothing, it even didnt start compiling. Stopped before that.

Its just bug somewhere. I dont have time to debug, i need to work on my projects.

I will remember these tips though.

[phibermon]

I will do my best to help if you still need it.

Although I've never understood why so many people have issues with Lazarus, for at least 2 years on multiple machines and multiple platforms fresh installs from the daily SVN snapshots have always worked for me first time. The occasional crash whilst debugging in the early days but no show stoppers.

Just tell it where FPC is, the sources and GDB and it's all hunky dory.

This is all on fresh installs of various Oses and on machines that have been used for years with many installs of lazarus, custom FPC setups etc

I'd love to know what people are doing their machines / installs that causes it to break so utterly. Try a snapshot. Uninstall Lazarus and any FPC you might of installed. Clear any environment variables that may be setting FPC paths etc

Edit : I've not tried the specifc builds you're referring to. Just ignore me. I've not personally had issues with Lazarus.

Also loving generics support in FPC, I'd use them extensively if it wasn't for the fact I've a vast code base with a consistent coding style that already has the things generics make easier, defined. Might go thru my code and replace all the stuff that's applicable with generics one of the days, assuming it doesn't obfuscate things too much.