1 of 1 people found this helpful
As ridiculous it may sound, we have not tried this. So, my advice to you would be using the cmake generators to generate the .mk files and port them to WICED. While porting you might come across some errors but still manually editing the .mk files to make it work seems to be the only way forward.
Thanks for your reply. That was my conclusion this morning, so now I am looking at cmake -G "Eclipse CDT4 - Unix Makefiles" ./ as the way to generate that MK file, but I don't know what it will generate and where the results will be stored.
Is that your suggestion too, to use "cmake -G" to generate at CDT4 Unix Makefile format? If not, are there other alternatives that you suggest?
Do you know how many MK files are made by the Generator, and now many MK files do I need for WICED to build? I seem to recall that there are several MK files in my folders.
I also found a converter called "cmake4eclipse" in the Eclipse Marketplace, but trying to import it with "Help->Install New Software" does not work, so I cannot check out that idea. Would you see if you can Install New Software called "cmake4eclipse" and let me know how you made it work? When I tried it, the "cmake-eclipse-helper" installed okay, but the "cmake4eclipse" failed.
Thanks, Garry Anderson.
The "cmake" generator (cmake -G "Eclipse CDT4 - Unix Makefiles"), creates a tree of make files called "cmake.install.cmake" and each file is like the attached file, and uses the files in its own directory. This is good, and it appears to be the MK file structure that I need,
BUT ... How can I modify Wiced-Eclipse "build" action to look for "cmake.install.cmake" files instead of MK files? Or, is there a command-line option to have the cmake command add "MK" extensions instead of "cmake" extensions?
Do I have to rename all the files, and any references that refer to them? It is a lot of work, so it seems better to simply change the way the "build" command works.
Thanks for your help.