You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are configuration scripts for installing on Condos with the GNU compiler in both optimized and debug mode. However, the only CMake script for Condos has the path for the optimized settings hard-coded.
@jeanlucf22 Should there be a second CMake script for installing in debug mode, or should it try to auto-detect whether you're in optimized or debug mode? I'd be happy to take care of this as a first contribution.
The text was updated successfully, but these errors were encountered:
The preferred option is to use cmake to build the main code, and autoconf for the base libraries. It may actually be the only one working. So autodonf scripts are really used only for the base libraries.
(cmake) build scripts are meant to be examples of how to build the code. They just happen to be the ones I often use. Debug vs optimize: this is the user's choice and should be in their own script. But it doesn't mean that additional scripts could not be added.
There are configuration scripts for installing on Condos with the GNU compiler in both optimized and debug mode. However, the only CMake script for Condos has the path for the optimized settings hard-coded.
@jeanlucf22 Should there be a second CMake script for installing in debug mode, or should it try to auto-detect whether you're in optimized or debug mode? I'd be happy to take care of this as a first contribution.
The text was updated successfully, but these errors were encountered: