Hi,
The extra targets are not a problem in such way that things woudn't
build - actually
everything builds OK with stock Filelists.cmake. I was worried to
use file as is
because of all the stuff it has in it, as these are my first steps
with cmake.
Also, I didn't know about EXCLUDE_FROM_ALL flag - one more lesson
learned.
Thanks,
Ari S.
On 3.3.2019 21.55, Dirk Ziegelmeier
wrote:
Hello Ari,
are these
targets a problem for you? They are defined with
EXCLUDE_FROM_ALL, so they are not built by default - only
when you need them. So there should be no problem for your
build??
Hi,
I have been integrating lwip into my own cmake-based build
in a larger project.
Before, when I was using Gnu Make, I used to include
Filelists.mk in my project
as it only provides some handy variables with source file
names.
I assumed that Filelists.cmake would be the same for cmake
world.
But it isn’t. In addition to variables like lwipcore_SRCS it
also defines
some cmake targets, which I don’t need in my builds.
Would the project consider splitting Filelists.cmake into
two files,
one that has only variables for source files names (like the
Gnu Make Filelists.mk does)
and an another one, which has rest of the stuff ? This would
make integration
easier.
Ari S.
_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel
_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel
|