>> http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_avoid_the_error_.22Arg_list_too_long.22_when_running_make.3F > so both the means suggested on that page dont apply to us. > the problem is very specifically for some compiler versions, > and i was looking for a native cmake solution that /does not/ depend > on a specific environment. > we're providing a larger framework, which in turn consumes > many upstream packages (some of which we are writing CMakeLists for, > but do not interfer with/change the code itself). > as the overall build is controlled by a superproject > (using external projects), the external project partially consume > other external frameworks. > now, if they are placed under an architecture directory > (mpi/release|debug/static|shared etc), the include paths > to the libraries tend to get longer and e.g. fail for > the intel compsuite 12, where the maximum argument buffer is 4k.
Can corresponding tools process the needed parameters also by passing them in dedicated input files? Would special file formats be usable for your software? > i know custom commands, and unfortunately, no they wont help in our situation. Why not? Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
