Content originally posted in LPCWare by bowerymarc on Sun Apr 14 20:21:27 MST 2013Thanks for the replies, but I'm still having the same problem. Some comments:
- both @Wouter and @wellsk assumed my problem was copying the projects into the workspace (an excellent suggestion, when I was Newbie I had puzzled over this option) without actually trying that to see the result... this is what I get when I import the two projects and try to compile the sdmmc project:
<code style="margin: 0px; line-height: normal; font-family: 'Courier New'; color: #103ffb;">22:38:36 **** Build of configuration Debug for project lpc43xx_hitex_eva_4350_periph_sdmmc ****</code> <code style="margin: 0px; line-height: normal; font-family: 'Courier New';">make -j4 all </code> <code style="margin: 0px; line-height: normal; font-family: 'Courier New';">make: *** No rule to make target `Y:/software/filesystems/fatfs/src/ff.c', needed by `fatfs/ff.o'. Stop.</code> <code style="margin: 0px; line-height: normal; font-family: 'Courier New'; min-height: 11px;">
</code> <code style="margin: 0px; line-height: normal; font-family: 'Courier New'; color: #103ffb;">22:38:37 Build Finished (took 891ms)</code>
- I also tried a fresh workspace, and a fresh workspace and fresh unzip of the archive, and a fresh workspace with a fresh download and unzip of the archive (LPCOpen 1.02). All give me exactly the same error
- it's great (for someone else...) that this might work with the 5.1.0 toolchain, but I'm using the latest 5.1.2_2065 toolchain and I'm not aware of anywhere I could even get earlier versions, I didn't see them on the code-red website. @Wouter if you're game perhaps you can upgrade and attempt the same compilation I am.
- the problem I'm having is on Win XP (SP2). Using the OSX toolchain (same version), everything compiles fine. Unfortunately, for some odd reason, the ULINK2 isn't supported on OSX (even though, it's a driverless HID peripheral).
- the info that I only need the board lib and the project of interest is great to know, and doesn't exist anywhere except this thread.... The quickstart guide has you importing <em>all</em> of the projects in your eval board directory. (Which, by the way, I also tried, and got the same error).
- the files it says it can't find during compilation, I can find by manually opening them with 'open declaration' right click. I.e. I got to rtc.c line 14 and select 'chip.h' and right click and select 'open declaration' which opens chip.h, and then select 'sys_config.h" on line 32 of chip.h and right click and select 'open declaration' and it opens sys_config.h. All of the errored files are openable this way. The only thing I can think of is that there's a disconnect somewhere deep in the project setup with the Include file relative pathnames, since chip.h isn't at the same level of the LPCOpen heirarchy as the project, maybe it's missing the board directory where sys_config.h is. There are benefits and drawbacks to putting relative pathnames in eclipse projects, there were of course engineered by whover made LPCOpen outside of eclipse, since within eclipse, it only writes absolute paths into the .project/.cproject files.
So... I'm still stuck.
Thanks again,
Marc
<code style="margin: 0px; line-height: normal; font-family: 'Courier New'; color: #103ffb;"></code>
<code style="margin: 0px; line-height: normal; font-family: 'Courier New'; color: #103ffb;"></code>
<code style="margin: 0px; line-height: normal; font-family: 'Courier New'; color: #103ffb;"></code>