afull’s ポイント

afull's ポイント

Total 42
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
+2
6月 22, 2016 Asked GNUARM-NONEV16.01-EABI Compiler Crash
+1
5月 25, 2016 Commented Hi, I'm sorry I deleted the workspace .metadata folder. This folder quickly becomes huge and as far as I can see contains only a few preferences, which I am quite happy to reset. I keep the workspace in a separate folder to the project files and it is not under version control. The archive file and include file bugs are also in V16.01. To reproduce the include file bugs simply generate a C++ static library project with -mfloat-abi=hard. Then add the following standard headers to one of the sample C++ files: #include #include #include #include #include #include #include #include If you try to build the project it will fail because E2Studio has failed to add any include paths. If you want the code to build then manually add the following paths: ${TCINSTALL}/arm-none-eabi/include ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION} ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION}/arm-none-eabi/fpu ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include-fixed Then in the compiler options add the option -std=gnu++11. Only then will the library compile. Using the V16.01 tool chain generate a C++ project changing only Floating Point ABI to Hard (there is no option for vfpv3). In order for it to link you have to manually change the option to vfp3. Then add gnu++11 option to the compiler settings and the include files to projectname.cpp & yet again it fails to link. As the documentation is as much use as a chocolate fire guard, the best option is to go to https://gcc.gnu.org/mirrors.html and download the source code to the appropriate GCC version (5.2 for V16.01). This is the only way that user's of E2Studio will be able to figure out what the include folders should be and how to initialise the C++ standard library. I have never had so many issues with the quality of the tool integration in any other IDE. I hope that future releases of E2Studio are better documented and address the issues with the project generators for the GNUARM-NONE-EABI Toolchain. Best regards, Adam
+1
5月 11, 2016 Commented Hi Darius, Thanks, however I believe that this documentation is for glibc. E2Studio uses newlib, so while some of it appears to apply there are bits missing from newlib. So C++ code which builds with glibc has errors with newlib, which would be easier to avoid if it were documented. Without any documentation I have had to use a trial and error approach to establish which archive files and library paths to use. Using the E2Studio project generator to make a C++ project with default options bar vfpu=hard adds the following archive search directories: Archive search directories "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/fpu/interwork" "${TCINSTALL}/arm-none-eabi/lib/fpu/interwork" And the following archive library files: ${BuildArtifactFileBaseName} gcc stdc++ And include directories: ${TCINSTALL}/arm-none-eabi/include ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include In order for the C++ to build and link I had to change the archive search directories to: "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/fpu" "${TCINSTALL}/arm-none-eabi/lib/fpu/interwork" And add the following include directories: ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION} ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION}/arm-none-eabi/fpu ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include-fixed Although the code links and runs OK without any documentation it is difficult to know if this is correct. Best regards, Adam.
+1
5月 9, 2016 registration
1 2
サポート