Recent

Author Topic: [SOLVED] The cleaning master  (Read 1409 times)

macfly

  • New Member
  • *
  • Posts: 13
[SOLVED] The cleaning master
« on: January 24, 2020, 03:48:33 am »
Hi friends,

The subject of topic is not a joke  8)

Any tips on why the compiler doesn't detect changes in the code?

I have to use "Clean up and build" at all times for the changes I just made to be applied.

"Smart linkable" checked and unchecked and same behavior.

Even with "Always Build" activated, it does not recognize the changes.

Lazarus 2.1.0
Windows 10  With SSD (if this is any clue)

Thanks for any suggestions

« Last Edit: January 24, 2020, 02:54:45 pm by macfly »

Handoko

  • Hero Member
  • *****
  • Posts: 5131
  • My goal: build my own game engine using Lazarus
Re: The cleaning master
« Reply #1 on: January 24, 2020, 03:53:54 am »
Did the issue only happen on Lazarus 2.1.0? Have you tried Lazarus 2.0.6 or lower versions? I meant I never have such problem, I'm using Lazarus 2.0.6. It sounds like a bug in Lazarus 2.1.0.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9794
  • Debugger - SynEdit - and more
    • wiki
Re: The cleaning master
« Reply #2 on: January 24, 2020, 04:06:32 am »
You are talking about units in your project, or in some package?

What is the project structure?

How many pas or pp files?
Do you use {$Include }?

Are all units in the same folder?

Have you done anything to any of the "path" settings in project (or package) options?

Thaddy

  • Hero Member
  • *****
  • Posts: 14205
  • Probably until I exterminate Putin.
Re: The cleaning master
« Reply #3 on: January 24, 2020, 08:28:27 am »
Autosave on? changes need to be saved before the compiler will recompile the changed units, so make sure they are saved.
Specialize a type, not a var.

MarkMLl

  • Hero Member
  • *****
  • Posts: 6676
Re: The cleaning master
« Reply #4 on: January 24, 2020, 09:21:49 am »
More than one copy of a unit open? I think I've seen something like that happen- not recently- when the debugger started opening extra copies of sourcefiles because of range errors etc. and for some reason they weren't handled as just a copied window.

MarkMLl
MT+86 & Turbo Pascal v1 on CCP/M-86, multitasking with LAN & graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

macfly

  • New Member
  • *
  • Posts: 13
[SOLVED] The cleaning master
« Reply #5 on: January 24, 2020, 02:54:25 pm »
I appreciate everyone's tips.

They gave me clues on where to look.

The problem was in the organization of my project.
Apparently Lazarus ignores the check for modifications if the project file is inside a folder included in the paths.

I'm writing Test cases and the project file was inside a folder included in Path

Code: [Select]
Root
 |---+ Source
       | all my .pas sources
       |----+ Tests
              |  all my tests .pas sources
              | Test projectFile (Tests.lpi)  <<-- project file inside a folder included in path

I reorganized the structure and the problem was solved.

« Last Edit: January 24, 2020, 03:06:52 pm by macfly »

MarkMLl

  • Hero Member
  • *****
  • Posts: 6676
Re: [SOLVED] The cleaning master
« Reply #6 on: January 25, 2020, 10:19:46 am »
Apparently Lazarus ignores the check for modifications if the project file is inside a folder included in the paths.

That rings a bell.

MarkMLl
MT+86 & Turbo Pascal v1 on CCP/M-86, multitasking with LAN & graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

 

TinyPortal © 2005-2018