Hi,
i had a project which was working with the previous version of openat (4.24 i think?)
I downloaded the new open at 2.0 and i re-ran the openat project wizard to recreate the make files etc…
but it keeps coming up with the following:
any ideas?
c:\OpenAT\IDE\MINGW\3.8.0.1\bin\make.exe: *** No rule to make target appli.o', needed bygcc
I think i got it going, i deleted every single file except the .c and .h and re-ran the wizard…
however, now i get these errors:
error: syntax error before ‘io_config’ (this refers to the line: adl_ioConfig_t io_config;)
error: ‘ADL_IO_Q2686_GPIO_31’ undeclared (first use in this function)
etc… etc… etc…
does old software need to be modified to work with the new openAT?
i read the RN_Open_AT_Software_Suite_v2_01_Customer_Release_Note.pdf and it has the following listed (on page6) which i cant find…
[12] Migration document WM_DEV_WUP_MEM_020
does anyone know where i can get it from? or if any other porting documents exist?
Now I know running the wizard should recreate the make file properly, but even if I deleted every file in the project folder aside from my inc and src I still had the same problem.
executable to generate
#------------------------------------------------------------------------------
SRC_C_LIST = \
Actions.c \
AlarmsIO.c \
Command_Parser.c \
Contacts.c \
Email.c \
Errorcheckers.c \
Events.c \
IdentifiersIO.c \
JP_Functions.c \
SMS.c \
Serial.c \
action_aaa.c \
cfg \
_appli.c \
cfg_entry_point.c \
cfg_gprs.c \
cfg_gsm_client.c \
cfg_gsm_server.c \
cfg_uart_client.c \
cfg_uart_server.c \
event_aaa.c \
main.c \
#------------------------------------------------------------------------------
# List of assembler files of the library or executable to generate
#------------------------------------------------------------------------------
SRC_ASM_LIST = \
you see the cfg_appli.c broke into two files for some reason(very strange I thought)
so I renamed the cfg_appli.c to problem.txt then back to cfg_appli.c (thinking that there may be a hidden charactor that somehow managed to sneak its way into the windows file name) and it appears I was right, because it worked after that.
One of the stranger annomalies I’ve seen, but I thought I’d share my experience.