Bill Hoffman pisze:
> Wojciech Migda wrote:
>
>> Hi again,
>>
>> this workaround seems to do a trick:
>>
>> in cmDependsC::WriteDependencies I've added a local variable to store
>> path to the source file being scanned for dependencies:
>>
>> std::string root_dir =
>> cmSystemTools::GetFilenam
In your top most CMakeLists.txt file you might want to try adding the
following:
# -- Setup output Directories -
SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY
${PROJECT_BINARY_DIR}/Bin
CACHE PATH
"Single Directory for all Libraries"
)
# - Setup the Execut
Wojciech Migda wrote:
Hi again,
this workaround seems to do a trick:
in cmDependsC::WriteDependencies I've added a local variable to store
path to the source file being scanned for dependencies:
std::string root_dir =
cmSystemTools::GetFilenamePath(this->LocalGenerator->Convert(src,
cmLo
Hi again,
this workaround seems to do a trick:
in cmDependsC::WriteDependencies I've added a local variable to store
path to the source file being scanned for dependencies:
std::string root_dir =
cmSystemTools::GetFilenamePath(this->LocalGenerator->Convert(src,
cmLocalGenerator::HOME_OUTPU
Wojciech Migda wrote:
Hi all,
I have a build system with several subtargets residing in respective
subfolders. What is important - I'm using common binary directory for
all targets. The command I use is:
ADD_SUBDIRECTORY( nth_subfolder common_binary_dir )
Each directory must be unique. Ther
some follow-up to my previous post:
I don't see an easy way to fix the presented problem within cmake
scripting mechanisms other than adding own script called at the setup
time for dependencies check and adding those dependencies to objects
using SET_PROPERTIES* directives.
However, as far as I c
Hi all,
I have a build system with several subtargets residing in respective
subfolders. What is important - I'm using common binary directory for
all targets. The command I use is:
ADD_SUBDIRECTORY( nth_subfolder common_binary_dir )
The common binary folder was chosen to have all static librari
