Hi Rutherther!
I think it's good idea to move away from C_INCLUDE_PATH, LIBRARY_PATH for the toolchain libraries (glibc, stdlibc++, ...), but what about other libraries? Those, as far as I can tell, have to be provided by a search path, as they cannot be compiled inside the toolchain. Or am I mistaken in this?
These search paths stay.
And if this is true, I think it would be good to still keep this CROSS_* convention
For other libraries than the standard ones there will be no real problems, as in Guix the build environments only provide the needed packages, so there shouldn’t be any problems. For cross-compilers used by guix build --target=… these CROSS… variables anyway collect the same paths, namely <package>/include and <package>/lib. So whatever the name of these variables is, it makes no difference. I also think that there won’t be many clashes between include files from packages for the host and include files from packages used with an embedded cross-compiler. I currently don’t see the real need. Even if you install several compilers into your profile, you certainly won’t install embedded source code packages into your profile. Or do you? Even on “usual“ Filesystem-Hierarchy-Standard systems no cross-compiler uses different environment variables for include paths. But to be honest, I'm not really sure about this for embedded cross-compilers yet. Whatever I did myself so far was all fine without these CROSS… variables. So I’d like to first try without as far as possible. Bye Stefan
