build with vs on windows#47
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Just FYI I built this locally using an environment as close as I could get to the azure environment and it worked (not sure why it's erroring out here though). These were the CMAKE settings: ...
cd build
cmake -G "Ninja" ^
-DCMAKE_BUILD_TYPE="Release" ^
-DCMAKE_CXX_STANDARD=17 ^
-DCMAKE_EXPORT_COMPILE_COMMANDS=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%LIBRARY_PREFIX% ^
-DFLANG_INCLUDE_TESTS=OFF ^
-DCMAKE_PREFIX_PATH:PATH=%LIBRARY_PREFIX% ^
-DLLVM_LIT_ARGS=-v ^
-DLLVM_CMAKE_DIR:PATH=%LIBRARY_LIB%\cmake\llvm ^
-DCLANG_DIR:PATH=%LIBRARY_LIB%\cmake\clang ^
-DMLIR_DIR:PATH=%LIBRARY_LIB%\cmake\mlir ^
-S ..\flangA few things from my local build:
Just some things to consider, |
|
Thanks for testing this out!
Azure agents are puny, resp. flang compilation has a monster memory footprint, and the default parallelism (or any parallelism actually) blows out the memory we have (including 8GB swapfile...)
Thanks, those seem to be leftovers, let's delete them.
The other variables don't hurt at the moment, so I'm inclined to leave them.
We definitely did need it when building with clang - AFAIU, the upstream flang build will decide to use uint128 based on whether the used compiler supports them - clang-cl does, msvc doesn't, so we need that variable for the former, not the latter (not 100% sure, but this is my understanding). |
it blows through azures available memory, despite the swapfile...
…nda-forge-pinning 2024.04.11.05.55.23
Trying to address #46