"Scanning for dependencies" is too slow

[larryli]

I tried to build the latest LVGL graphics library with built-in Windows driver.
There are no big issues during the build，except for a few compatibility warnings.
But the IDE show the "Scanning for dependencies" message, when I add the lvgl source file one by one. This is too slow, and it maybe unresponsive.

[Vortex]

Hi larryli,

The src folder of the zip file offering the source code contains 110 folders and 576 files. What's the speed of your processor?

[larryli]

Hi larryli,

The src folder of the zip file offering the source code contains 110 folders and 576 files. What's the speed of your processor?

Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
Physical Memory: 16.0 GB (DDR4 1600 2x8GB)
SSD: 512GB (NVMe 1.4), System partition uses NTFS, and source files place to a ReFS volume
System: Microsoft Windows 11 Home (23H2)
Pelles C: 12.00

[TimoVJL]

Interesting file system you use:
Resilient File System (ReFS) overview

[larryli]

Interesting file system you use:
Resilient File System (ReFS) overview

I use the Dev Home App https://apps.microsoft.com/detail/9N8MHTPHNGVV, and doc at https://learn.microsoft.com/en-us/windows/dev-drive/.

[larryli]

Complete project file. the simple project file was generated using the script, and it took the whole night to update the dependencies

[John Z]

Hi larryli,

So, 'slow' is relative - what system performed faster than Pelles?

Also have you tried moving the files to the common SSD NTFS file system and tried that?

John Z

[larryli]

Also have you tried moving the files to the common SSD NTFS file system and tried that?

There is no difference.

[frankie]

No way to reduce time.
The reasons are 2. This code has so many nested headers that the time delay is inevitable. My opinion: "it's good to slice code in many modules to make more efficient library use, but the sparse definitions in hundreds of headers and the heavy macro coding is too much for me" (polite for bad coding? probably, even for embedded programming almost all compilers have a 'separate segment by function' to avoid wasting program memory, so this proliferation of headers is not necessary).
The second problem is the PellesC browser that surely isn't designed for such a mess (here would help a lot the MSVC precompiled headers...).
A suggestion to not wait, open a cmd window in the project folder and try:

Code: [Select]

> POVARS32
>pomake /F lvgl-9.0.0.ppj
If you're compiling for 64bits:

Code: [Select]

> POVARS64
>pomake /F lvgl-9.0.0.ppj