In our project file, we are using the
Call a C function custom action. Since this requires using absolute paths and since we cannot guarantee all developers use the same path for their code repositories, we put the C file (and identically named header) in a folder, thus using a UNC path in the PB project to access the file on the network. This has been working for years but unfortunately seems to be broken after upgrading to PB 2021.0 since we now get the following compilation error:
<PATH>\bin\mainscript.c(24): fatal error #1035: Can´t find include file "\\<SERVER>\paquetBuilderScripts\updateEnvironment.h". COMPILATION ERROR A fatal error has occurred: Compilation Failed for Script "<PATH>\bin\mainscript.c" Compilation aborted; The package has NOT been created. FATAL ERROR: Compilation Error: Compilation Failed for Script "<PATH>\bin\mainscript.c"
We noticed that using a local absolute path does not produce the issue, but we really need a fix to make this work again with UNC paths (being able to use relative paths could also help)
We also noticed the following in the change history:
- New 64-bit edition of Paquet Builder available: this removes the 4 GB memory limit for 7-zip compression and it uses the latest 64-bit C compiler available (v10).
Could this issue be related to the new C compiler?
Thanks for your help, we are currently blocked since we can no longer build the project (we were previously using the hot fix for the timestamping issue)…