a combination of the above..
somefile.h
"file1", "file2", "file3"
somefile.c
...
const char *files[] = {
#include "somefile.h"
};
would be easiest for cmake to parse the .h... I would think...
otherwise no; might be easier to maintain the list in the cmake and stuff
it into the C usin
I don't think it needs to be a custom command, you just do it inline.
See e.g.
FILE(STRINGS, ...)
http://www.cmake.org/cmake/help/v3.0/command/file.html
or FILE(READ, ...)
http://www.cmake.org/pipermail/cmake/2007-May/014222.html
There are several gotchas related to quoting. Ping the list if you
On Wed, Aug 5, 2015 at 3:17 PM, Owen Alanzo Hogarth wrote:
> I can put those in some type of array in my c source code. Now is it
> possible to send that list back to cmake at build time so that it can copy
> those files to the binary tree on each build?
You can write a script that parses the C s
I know it's possible to send variables into your c source code from the
cmake tutorials where you set the version.
let's say in your c source code you access some resource files that are
located in your source tree under a resources folder.
I can put those in some type of array in my c source cod
