> Lead PM for the VC++ team at Microsoft here. I just wanted to echo
> Nagy-Egri’s message.
>
>
>
> We are very interested in learning more about your current
> edit-build-debug experience for C++ apps or libs using CMake. Whether
> you’re developing on Windows or not, using VS or not today, we
> > This sounds more like an install phase... to bring the whole package
> > together in one appropriate place.
> >
> > if( WIN32 )
> > INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION bin
> > ARCHIVE DESTINATION lib )
> > else( WIN32 )
> > INSTALL( TARGE
> This sounds more like an install phase... to bring the whole package
> together in one appropriate place.
>
> if( WIN32 )
> INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION bin
> ARCHIVE DESTINATION lib )
> else( WIN32 )
> INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION
hi,
i'm wondering, is it possible to generate msvc solutions for windows
kernel mode drivers?
afaict, the generated projects would have to use a specific platform
toolset:
WindowsKernelModeDriver8.1
but also some other specific entries, like:
Driver
KMDF
maybe it be possible/easy/reasonable to
hi all,
a combination of question and feature request:
i'm using a highly customized shell script to generate Info.plists on
osx. this build script has to make use of the usage requirements of the
corresponding target and it is called via a POST_BUILD custom command.
however this conflicts with
hi all,
i'm having some troubles, trying to install osx bundles:
app bundles:
installing an app bundle target (created with MACOSX_BUNDLE and property
BUNDLE=1) will install (a) the bundle and (b) the executable (which is
usually found in Contents/MacOS). in a way, i'd only expect the bundle
to b
hi david,
> I just created a test project "t2" with Xcode itself, and in the
> projects source file "t2-Info.plist", I added a "Get info string" key
> with a value of "This is the ${CONFIGURATION} build."
>
> Then, after I build the Debug config, and inspect the generated bundle,
> the Info.plist
hi all,
i'm trying to build an Info.plist file with some information based on
the build configuration (DEBUG or RELEASE). is this possible for
multi-configuration generators like xcode?
it does not seem to be possible to use different
MACOSX_BUNDLE_INFO_PLIST files for different configurations, n
hi all,
the make/ninja files and visual studio project seem to be rebuilt
automatically when some CMakeLists.txt files change. this does not seem
to be the case for xcode projects, though. to regenerate the project, i
need to buid the ZERO_CHECK target explicitly.
is this a bug or a feature?
thn
hi all,
i'm trying to use the iOS.cmake toolchain file from [1]. it works fine
with cmake-2.8.12.2, but fails with cmake-3.0 (today's master), which
gives me:
-->8---
CMake Error at CMakeLists.txt:16 (project):
The CMAKE_C_COMPILER:
gcc
is not a full path and was not found in th
hi,
i'm using usage requirements to pass on dependencies in the build system.
--
set(MY_DEBUG_LIB libDebug.lib)
set(MY_RELEASE_LIB libRelease.lib)
target_link_libraries(mylib
debug ${MY_DEBUG_LIB}
optimized ${MY_RELEASE_LIB})
add_executable(myapp somesrc.cpp)
target_link_libraries( m
hi all,
from my understanding it is possible to add sources to an osx bundle,
which are then automatically copied e.g. to the Resource folder or the
like. however i'm in the situation that i have to move some build
targets (executables and dylibs) into the bundle. what is the best way
to achieve t
> Have you tried quotes in your message() so it doesn't remove the semi-colons?
> message("${x}")
ah, that explains my confusion of the missing semi-colon
thanks, tim
--
t...@klingt.org
http://tim.klingt.org
Relying on the government to protect your privacy is like asking a
peeping tom to inst
hi all,
i am trying to write a ctest script, compiling for different OSX architectures.
the CMAKE_OSX_ARCHITECTURES option uses the semicolon to distinguish between
architectures, but my attempts to generate the argument string with semicolons
haven't been successful, it seems they are not esca
hi all,
i am using mingw to cross-compile to windows. however the build names, which
appear in the cdash dashboard are somehow inconsistent. for native builds, the
naming is PLATFORM-CXXCOMPILER. the however the cross-compiled version is named
Win32-make, although the name of the c++ compiler i
hi all,
i am trying to run ctest with the qemu cpu emulator: so if i am compiling a
test
case myTest, it is usually simply called with `./myTest'.
is it possible to wrap this into a program, so that it calls `qemu-ARCHITECTURE
-cpu CPUTYPE ./myTest'?
thanks, tim
--
t...@klingt.org
http://tim
hi all,
i am currently trying to adapt a cmake build system to build an osx app.
the specific code is:
INSTALL(CODE "
include(BundleUtilities)
fixup_bundle(\"${CMAKE_CURRENT_BINARY_DIR}/${myappbundlename}.app\" \"\"
\"${CMAKE_CURRENT_BINARY_DIR}\")
"
COMPONENT Runtime)
however it d
hi all,
out of curiosity, why is COMPILE_FLAGS a target property, while
COMPILE_DEFINITIONS is both a directory and a target property?
currently, i am setting CMAKE_CXX_FLAGS manually to achieve the behavior,
that i need for my application ...
thanks, tim
--
t...@klingt.org
http://tim.klingt
hello michael,
thanks a lot ... i needed to adapt it a bit for my applications, but it
works like charm now ...
thanks, tim
--
t...@klingt.org
http://tim.klingt.org
Happiness is a byproduct of function, purpose, and conflict; those who
seek happiness for itself seek victory without war.
Wil
>> from my limited understanding of the linking process, it should link with
>> -lcommon instead of using ../common/libcommon.so, since the rpath is
>> already set to ../common. but how can i tell cmake to do this?
>
> As far as I can see this is ok. At least its the same in the cmake
> projects I
hi all,
i've got some troubles to byte-compile emacs lisp files with cmake.
basically, i need to do the following
- copy source file to the build directory
- compile the elc file with: "emacs -batch -f batch-byte-compile
/path/to/source.el"
- add an install rule to install the generated elc file
hi andreas,
>> common/libcommon.so
>> target1/target1
>> target2/target2
>>
>> both target1 and target2 are linked with libcommon, both work fine in the
>> build directory, the libraries are resolved correctly.
>>
>> after installing them, they are formatted like:
>> $PREFIX/lib/libcommon.so
>>
hi all,
i am trying to write a cmake build system for an existing project and have
some troubles with linking of shared libraries.
basically, my directory layout of the targets is the following:
common/libcommon.so
target1/target1
target2/target2
both target1 and target2 are linked with libcomm
23 matches
Mail list logo