Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
See Also
Discussion Groups | LPC2000 | GNU libc header files and Crossworks
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
GNU libc header files and Crossworks - Kevin Townsend - Oct 23 19:45:01 2008
I am trying to port a GCC-based project to an lpc2148 and Crossworks,
and noticed that there are many includes that are, well, not included
with Crossworks (all of the items below, for example).
#include <_ansi.h>
#include
#include
#include
#include
#include
#include
#include
#include
#include
Is there any way that they can be supported inside Crossworks? I've
gotten quite used to using this IDE, and am not really eager to have
to change. I've tried downloading the appropriate files and adding
them to the solution, but I get way too many naming conflicts since
Rowley has implemented some functionality in their own C headers.
Anyone else have any luck with this?
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
and noticed that there are many includes that are, well, not included
with Crossworks (all of the items below, for example).
#include <_ansi.h>
#include
#include
#include
#include
#include
#include
#include
#include
#include
Is there any way that they can be supported inside Crossworks? I've
gotten quite used to using this IDE, and am not really eager to have
to change. I've tried downloading the appropriate files and adding
them to the solution, but I get way too many naming conflicts since
Rowley has implemented some functionality in their own C headers.
Anyone else have any luck with this?
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
RE: GNU libc header files and Crossworks - Paul Curtis - Oct 27 5:47:28 2008
Hi,
> I am trying to port a GCC-based project to an lpc2148 and Crossworks,
> and noticed that there are many includes that are, well, not included
> with Crossworks (all of the items below, for example).
>
> #include <_ansi.h>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include Is there any way that they can be supported inside Crossworks?
If you write the implementation, of course!
> I've
> gotten quite used to using this IDE, and am not really eager to have
> to change. I've tried downloading the appropriate files and adding
> them to the solution, but I get way too many naming conflicts since
> Rowley has implemented some functionality in their own C headers.
There's no way that will work,
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> I am trying to port a GCC-based project to an lpc2148 and Crossworks,
> and noticed that there are many includes that are, well, not included
> with Crossworks (all of the items below, for example).
>
> #include <_ansi.h>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
If you write the implementation, of course!
> I've
> gotten quite used to using this IDE, and am not really eager to have
> to change. I've tried downloading the appropriate files and adding
> them to the solution, but I get way too many naming conflicts since
> Rowley has implemented some functionality in their own C headers.
There's no way that will work,
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )