Hello,
I’m new in m2m studio and i want to know 2 things :
1 - how i can add a library in m2m stdio ?
2- i can use the existing project developed by open AT wizard directly ?
Thank you .
Regards !
I’ve just been trying that, and it doesn’t seem to work. 
I seem to recall that there was something in the release notes about it, but I haven’t checked that yet…
Thank you ,
it’s not work for me too , what about to add libray , you have an idea .
hello ,
i found how i can add the library but only for ARM_ELF_GCC_DEBUG 
( but not for MinGW_debug 
) , here is the procedure :
Open the Project > Properties > C/C++ General > Paths and symbols > References page
For each item in the Configuration drop-down list:
Check the related build configuration in the library project to be referenced.
Click the Apply button
Apply your modifications by using the OK button.
Linker additional library input
In order to link the final application versus the libraries provided by referenced projects, you have to modify the linker settings.
Open the Project > Properties > C/C++ Build > Settings > Tool Settings page
Then, select the linker tool (depending on the used toolchain) and go to the Miscellaneous options category.
For each item in the Configuration drop-down list:
Browse to the desired library file in the workspace, for the related build configuration.
Click the Apply button
Apply your modifications by using the OK button.
Notes:
Obviously, the library files have to be built at least one time in order to be able to browse for them.
Some toolchains (as ARM ELF GCC) take care of the library link order: if a library (lib1) calls functions provided by another library (lib2), lib1 has to be
GOOD LUCK !
The procedure is quite the same for MinGW configuration…
You have to use the Open AT IDE V1 projects import wizard in order to reuse one of your former projects.
Please elaborate if you have issues, since there are not known bugs anymore on this feature…
Thanks.
Yes, I did that.
I’ll have to try it again to get the exactl details.
IIRC, if I just ran the Wizard on the “main” project, it didn’t find the Library project correctly;
If I ran the Wizard on the Library project first, its output folder then didn’t match the path expected by the “main” project…
Please retry with 1.0.2 release: it sounds like bugs resolved since the 1.0.0 one.
I am already using 1.0.2
So please give us more details on the failing use case… 