For the "Unix Makefiles" generator, there's already a link.txt in
/CMakeFiles/.dir
Tamas
--
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
Thanks! I missed that property.
Tamas
On Thu, Apr 7, 2016 at 4:13 PM, Brad King <brad.k...@kitware.com> wrote:
> On 04/07/2016 10:03 AM, Tamás Kenéz wrote:
> > CMake uses "-isystem" on the compiler command line for the
> > INTERFACE_INCLUDE_DIRECTORIES of impor
Environment: CMake 3.5, linux, g++
CMake uses "-isystem" on the compiler command line for the
INTERFACE_INCLUDE_DIRECTORIES of imported libraries.
Unfortunately including a header via an isystem path suppresses warnings
emitted from the header, such as warnings caused by expansions of macros
ete nonsense!
I agree and that's why I think cmake ini files is a good idea.
Tamas
On Tue, Mar 15, 2016 at 3:25 AM, Ruslan Baratov <ruslan_bara...@yahoo.com>
wrote:
> On 15-Mar-16 02:42, Tamás Kenéz wrote:
>
> I also doubt this belongs to upstream. But you could write a sin
I also doubt this belongs to upstream. But you could write a single,
generic script which forwards its arguments to cmake and also accepts and
processes the additional parameters along the way. I don't think we'd lose
anything:
cmakeini -c ipad -H. -DTHIS_WILL_BE_FORWARDED=AS_IT_IS
This is
That's great and really does open a new world for IDEs!
Tamas
On Sun, Jan 24, 2016 at 11:44 PM, Stephen Kelly wrote:
> Hi,
>
> I just made a blog and video about the advanced features and possibilities
> that a daemon mode for CMake can bring:
>
>
It seems that the names of the PRIVATE dependencies of a library are not
affected by either the NAMESPACE option or the EXPORT_NAME property. A
minimal example:
add_library(one STATIC ...)
add_library(two STATIC ...)
target_link_libraries(two PRIVATE one)
install(TARGETS one two
Looking at what kind of mistakes the newcomers make, I think it's rather
the global workflow and the roles of certain key variables/properties they
don't get.
At first their problem is not that they can't make a for-loop or increment
a variable. It's that they don't understand how the build and
Charles,
I'd like to comment on a minor issue:
CMakeLists.txt files don't specify user-specific data like source and build
dirs (for a reason) yet your POC listfile contains this line:
cmake.init("Ninja", "/media/dev/src/cmaketest",
"/media/dev/build/cmaketest")
which sets the source and
MMAND} --build)
run_cmake_command(build-no-cache
--
2.2.1
On Fri, Oct 2, 2015 at 2:45 PM, Brad King <brad.k...@kitware.com> wrote:
> On 10/02/2015 08:00 AM, J Decker wrote:
> > On Fri, Oct 2, 2015 at 4:40 AM, Tamás Kenéz wrote:
> >> In script mode it seems that all t
In script mode it seems that all the CMAKE_[CURRENT_](BINARY|SOURCE)_DIR
variables are set to the current working directory.
Is this something we can rely on and it could be added to the documentation?
Tamas
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
> but I doubt the non-CMake ones generate SDL2Config.cmake files.
neither of them generates, not even the CMake one
On Wed, Sep 30, 2015 at 5:11 PM, Ben Boeckel
wrote:
> On Wed, Sep 30, 2015 at 10:22:47 -0400, Brad King wrote:
> > With regard to SDL2, the proper way to
Thank you, I was not aware of the EXPORT_NAME target property.
Tamas
On Tue, Sep 15, 2015 at 7:36 PM, Stephen Kelly <steve...@gmail.com> wrote:
> Tamás Kenéz wrote:
>
> >> For example, if an ALIAS can be IMPORTED, does it makes sense that it
> can
> > be
> >
> For example, if an ALIAS can be IMPORTED, does it makes sense that it can
be
> exported with export() and install(EXPORT)?
Yes: couple of months ago I was adding install(EXPORT) to an existing
CMakeList. The name of the library target which I had to export was not
correct as export target name
time where the generator expressions can be resolved.
Thanks,
Tamas
(sorry for not replying-to-all in previous email)
On Fri, Jul 17, 2015 at 5:41 PM, Brad King brad.k...@kitware.com wrote:
On 07/16/2015 11:29 AM, Tamás Kenéz wrote:
Well, it seems that `BundleUtilities` can't expand a single
the
`INTERFACE_LINK_LIBRARIES`
property and also resolves the $CONFIG, $NOT and $0|1: generator
expressions. I found no elegant way to resolve all generator expressions
(`file(GENERATE ...)` can't be used since it does not output the resolved
content instantly).
Tamas
On Wed, Jul 15, 2015 at 5:56 PM, Tamás
I've just read the discussion at
http://www.cmake.org/Bug/view.php?id=15299 about
the deprecation of CMakeExpandImportedTargets. I guess it means no fixes to
it.
I'm checking BundleUtilities as suggested there.
Tamas
On Wed, Jul 15, 2015 at 5:56 PM, Tamás Kenéz tamas.ke...@gmail.com wrote
The CMakeExpandedImportedTargets module used only the deprecated
IMPORTED_LINK_INTERFACE_LIBRARIES property to resolve transitive
dependencies.
Since the current `install(EXPORT ...)` command generates target files that
populate INTERFACE_LINK_LIBRARIES instead, the expand module was not
working
The documentation states that OBJECT libraries may not be [...] used in the
right hand side of target_link_libraries().
However it turns out that they can't be used on the left hand side either:
add_library(objlib OBJECT ...)
target_link_libraries(objlib dep-of-objlib)
Result:
Hi,
FindMatlab used dash for its internal headers.
This commit replaces caret-headers with double-quote-headers and replaces
dash-headers with caret-headers.
On top of release.
Tamas
0001-Help-fix-FindMatlab-section-headers.patch
Description: Binary data
--
Powered by www.kitware.com
Hi,
The search path rule #5 reads:
Search project build trees recently configured in a cmake-gui(1). This can be
skipped if
NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is
building
multiple dependent projects one after another. (This step is implemented only
Are you interested in working on a patch for this?
Yes, I'd give it a try. I signed up to Mantis, account: tamas.kenez so
you can assign it to me. I guess that's the next step.
Thanks,
Tamas
On Fri, Apr 17, 2015 at 2:01 PM, Brad King brad.k...@kitware.com wrote:
On 04/16/2015 05:54 AM, Tamás
The https://public.kitware.com/Bug/view.php?id=15231 feature request
proposes a new feature to make find_package to attempt CONFIG mode
first.
On 10/31/2014 01:30 PM, Brad King wrote:
I think the main challenge will be how to format error messages when
neither mode finds anything for a
23 matches
Mail list logo