View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011332CMakeCMakepublic2010-10-19 06:552011-01-12 07:42
ReporterRolf Eike Beer 
Assigned ToBrad King 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionCMake 2.8.4Fixed in VersionCMake 2.8.4 
Summary0011332: No dependency from ADD_CUSTOM_COMMAND to external project
DescriptionThe idea is like this: we have an project that generates a couple of
files. In a special configuration of another project we need those files
as input for a special build step. Those step will take those files,
mangle them and will generate a source file at the end. I simulate this by a simple copy below. This is then added as usual to a library (in my example below to a executable, but that doesn't matter). When I run the example below I get:

[ 80%] Built target Subdir_Build
make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'.

The project "Subdir_Build" indeed exists, as "make Subdir_Build" runs fine. And it looks for me as it is properly build before the target depending on it. I have found no way to set a dependency on the external project (tried ADD_CUSTOM_COMMAND(DEPENDS), ADD_DEPENDENCIES, and SET_SOURCE_FILES_PROPERTIES). If CMake can't do this it should give at least an error at CMake time.

Put this into CMakeLists.txt
=== snip ===
PROJECT(MaindirThing C)



                PREFIX "${CMAKE_CURRENT_BINARY_DIR}/build_subdir"
                SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/subdir"
                INSTALL_DIR "${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install"

        OUTPUT "main.c"
        ARGS -E copy ${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install/foo
        DEPENDS Subdir_Build

ADD_EXECUTABLE(simple_exe main.c)
=== snap ===

And this goes to subdir/CMakeLists.txt
=== snip ===


FILE(WRITE ${CMAKE_CURRENT_BINARY_DIR}/foo_file "int main(void)\n{\n
return 0;\n}\n")

=== snap ===
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
has duplicate 0012057closedBrad King add_custom_command can not depend on a custom target 

-  Notes
Michael Wild (reporter)
2010-10-19 07:08
edited on: 2010-10-19 07:28

AFAIK this is a documentation bug. The DEPENDS option of ADD_CUSTOM_COMMAND only works for top-level targets producing a file (i.e. ADD_EXECUTABLE and ADD_LIBRARY). It does not work with custom targets. For this one needs to create a special custom target which DEPENDS on the custom command, and then use ADD_DEPENDENCIES to make the custom target depend on the external project.

This has been discussed on the mailing list already: [^] Eike (the OP and reporter) so far hasn't answered the question whether it works with the custom target.

Rolf Eike Beer (developer)
2010-10-19 09:12

I tried:

ADD_CUSTOM_TARGET(Subdir_Build_Foo DEPENDS Subdir_Build)
     DEPENDS Subdir_Build_Foo)

I also tried


Nothing worked.
Michael Wild (reporter)
2010-10-19 09:32


ADD_DEPENDENCIES(build_main Subdir_Build_Foo)

Always use absolute paths when dealing with custom commands!
Rolf Eike Beer (developer)
2010-10-19 10:40

Yes, this works. But honestly, this is butt ugly and beyond the imagination of everyone reading the documentation. Especially since all other ways do not give any error at CMake time but cause build failures.

I still wonder if the Subdir_Build dependency is guaranteed to be built before the main.c dependency when doing parallel builds.
Michael Wild (reporter)
2010-10-19 11:15

It may be ugly, that's true, and it's also not very intuitive, and consequently the documentation of ADD_CUSTOM_COMMAND should be amended and that of ExternalProject_Add could be expanded to explain this pattern.

Also, you can "un-uglify" this if main.c is used in another top-level target:

ADD_DEPENDENCIES(main Subdir_Build_Foo)

This causes Subdir_Build_Foo to be built before the main target.

It works for me in parallel builds.
Rolf Eike Beer (developer)
2010-10-19 12:01

What I need is that it is build before main.c. In real life that is no simple copy operation but mangling of the output of the external command.
Michael Wild (reporter)
2010-10-19 13:23

Ah, yes, sorry about that. But on the up-side, you can use that custom target to provide a convenience target, e.g:

Brad King (manager)
2010-12-08 17:38

I published a fix:;a=commitdiff;h=ced1d5ec [^]

It depends on its parent commit for some minor refactoring:;a=commitdiff;h=e30a775f [^]

- Issue History
Date Modified Username Field Change
2010-10-19 06:55 Rolf Eike Beer New Issue
2010-10-19 07:08 Michael Wild Note Added: 0022532
2010-10-19 07:09 Michael Wild Note Edited: 0022532
2010-10-19 07:09 Michael Wild Note Edited: 0022532
2010-10-19 07:28 Michael Wild Note Edited: 0022532
2010-10-19 09:12 Rolf Eike Beer Note Added: 0022534
2010-10-19 09:32 Michael Wild Note Added: 0022535
2010-10-19 10:40 Rolf Eike Beer Note Added: 0022540
2010-10-19 11:15 Michael Wild Note Added: 0022541
2010-10-19 12:01 Rolf Eike Beer Note Added: 0022543
2010-10-19 13:23 Michael Wild Note Added: 0022544
2010-11-10 13:11 David Cole Assigned To => David Cole
2010-11-10 13:11 David Cole Status new => assigned
2010-11-10 13:11 David Cole Target Version => CMake 2.8.4
2010-12-08 16:43 Brad King Assigned To David Cole => Brad King
2010-12-08 17:38 Brad King Note Added: 0023827
2010-12-08 17:39 Brad King Status assigned => closed
2010-12-08 17:39 Brad King Resolution open => fixed
2011-01-12 07:42 David Cole Fixed in Version => CMake 2.8.4
2011-04-08 08:56 Brad King Relationship added has duplicate 0012057

Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker