My appologies, I see there is a README.cmake. I'll read it and see how it goes.
Don On Tue, Jun 26, 2018 at 12:42:04PM -0700, Don wrote: > I saw discussion of cmake, but not that it was ready for use. > > Trying to use it gives an error for _exit and newlib. > > I have used arm-none-eabi-gcc, ld, etc. along with libnewlib-arm-none-eabi > for several other projects. Does this cmake setup use those, the old path > to the ST Library, or something else??? > > It also looks like this setup is using the "standard" semihosting code > instead of the customized code in the older files. > > I think the creator of this needs to write the README file for it. > > Don > > --------------------------------------------------- > build $ cmake .. > -- The C compiler identification is GNU 4.9.3 > -- The ASM compiler identification is GNU > -- Found assembler: /usr/bin/arm-none-eabi-gcc > -- Check for working C compiler: /usr/bin/arm-none-eabi-gcc > -- Check for working C compiler: /usr/bin/arm-none-eabi-gcc -- broken > CMake Error at /usr/share/cmake-3.5/Modules/CMakeTestCCompiler.cmake:61 > (message): > The C compiler "/usr/bin/arm-none-eabi-gcc" is not able to compile a simple > test program. > > It fails with the following output: > > Change Dir: > /home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeTmp > > > > Run Build Command:"/usr/bin/make" "cmTC_6fca0/fast" > > /usr/bin/make -f CMakeFiles/cmTC_6fca0.dir/build.make > CMakeFiles/cmTC_6fca0.dir/build > > make[1]: Entering directory > > '/home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeTmp' > > > Building C object CMakeFiles/cmTC_6fca0.dir/testCCompiler.c.o > > /usr/bin/arm-none-eabi-gcc -o CMakeFiles/cmTC_6fca0.dir/testCCompiler.c.o > -c > > /home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeTmp/testCCompiler.c > > > Linking C executable cmTC_6fca0 > > /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_6fca0.dir/link.txt > --verbose=1 > > /usr/bin/arm-none-eabi-gcc CMakeFiles/cmTC_6fca0.dir/testCCompiler.c.o -o > cmTC_6fca0 > > > > /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/libc.a(lib_a-exit.o): > In function `exit': > > > > /build/newlib-5zwpxE/newlib-2.2.0+git20150830.5a3d536/build/arm-none-eabi/newlib/libc/stdlib/../../../../../newlib/libc/stdlib/exit.c:70: > undefined reference to `_exit' > > collect2: error: ld returned 1 exit status > > CMakeFiles/cmTC_6fca0.dir/build.make:97: recipe for target 'cmTC_6fca0' > failed > > make[1]: *** [cmTC_6fca0] Error 1 > > make[1]: Leaving directory > > '/home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeTmp' > > > Makefile:126: recipe for target 'cmTC_6fca0/fast' failed > > make: *** [cmTC_6fca0/fast] Error 2 > > > > > > CMake will not be able to correctly generate this project. > Call Stack (most recent call first): > CMakeLists.txt:53 (project) > > > -- Configuring incomplete, errors occurred! > See also > "/home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeOutput.log". > See also > "/home/don/Radio/Digital/FreeDV/Source/SVN/codec2-dev/stm32/build/CMakeFiles/CMakeError.log". > > > --------------------------------------------------------------------------------- > > > > On Wed, Jun 27, 2018 at 04:25:54AM +0930, David Rowe wrote: > > Hi Don, > > > > We are transitioning to a new Cmake based Makefile system for the stm32, > > that Richard has been working on. This was presented a few weeks ago > > (14 June) on this list but you may have missed it as I think you first > > approached us about then. > > > > The idea is to retire the current stm32/Makefile once we have tested > > images from the Cmake system, in particular a working sm1000.bin. > > > > Pls see README.cmake, and if you haven't done so already, try the Cmake > > build system for the stm32. > > > > Feel free to documenting the Cmake build system, and add your own unit > > test programs as targets. > > > > Cheers, > > > > David > > > > On 27/06/18 03:22, Don wrote: > > > The stm32/Makefile has rules to download and extract the ST provided > > > library for STM32F4. The location specified > > > > > > http://www.st.com/resource/en/firmware/stm32f4_dsp_stdperiph_lib.zip > > > > > > does not work for me. However it was easy to find the file and get it. > > > Now I have to have a hacked Makefile that comments this stuff out. That > > > makes it awkward to make other changes and get them checked in. > > > > > > Downloading this library is a one-time thing when you start working on > > > this code. In fact I don't think you want to get a new version if it > > > ever appears unless you are ready for it. So this does not need to be > > > in the Makefile. > > > > > > What I'd like to do is to put instructions for downloading the library > > > into the README file and take this part out of the Makefile. I'll also > > > have the Makefile use an ENV value for the location if set, otherwise > > > use the default location from the README. > > > > > > Does that work for people?? > > > > > > Don Reid > > > > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Freetel-codec2 mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Freetel-codec2 mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
