Hello Mirek,

I think I found something interesting: when compiling in "verbose", all paths to UppHub packages get included although I have only included one in my application package dependencies.

So if I have same packages present in UppHub and in another nest (both nests present in nest config paths) ... things will probably get nasty

When including external code, internal includes are some times necessary. If not, it would be necessary to change the includes of the external code by hand. I prefer to maintain the original code untouched.

koldo wrote on Tue, 04 March 2025 09:51

When including external code, internal includes are some times necessary. If not, it would be necessary to change the includes of the external code by hand. I prefer to maintain the original code untouched.

I agree...

Just investigating all possible loopholes. But my guts feeling is that possible problems with builder ignoring changes are not include path related...

Would be nice to have more info...

Mirek

Hey, so I have found and fixed one problem with dependencies:

In Win32, include file names can have different case from actual files (e.g. Header.h and #include "header.h"). There is a caching mechanism for filetimes to speed things up that was not ready to cope with this.

Now fixed: https://github.com/ultimatepp/ultimatepp/commit/4315ff493bc2 94e2dc2707062be95b998376768f

Can this be the problem?