Re: waf: wil the new build system copy header files to include as autoconf?

On Sun, May 01, 2016 at 11:44:23PM +, Amar Takhar wrote: > On 2016-04-30 23:50 +0800, printk wrote: > > Hi, will the new build system copy the headers to include too? > > No, the new build system which you can see here: > > https://git.rtems.org/amar/waf.git/

waf: wil the new build system copy header files to include as autoconf?

Hi, will the new build system copy the headers to include too? ... duhuanpeng. u74147＠gmail.com ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

codingstyle: usage of #include and #include "head.h"

What is the difference in RTEMS? there are code use #include "xxx.h" reference to xxx.h not located in the current folder. how about just use #include "xxx.h" to include the file in current folder? and use #include to include files in -isystem -I... this usage find in cpukit/lib/networking/

dtc: compile error

Hi, I use this cflags to compile rtems/cpukit/dtc/*, I get error message below: - - - - - - - - - - - - - - - - - - - - make -f ./scripts/Makefile.build obj=cpukit/dtc/libfdt arm-rtems-gcc -Wp,-MD,cpukit/dtc/libfdt/.fdt_addresses.o.d -Ic/src/lib/libbsp/shared/include -Ic/src/lib/libcpu/arm/s3

Re: when the getcwd.c is compiled?

On Wed, Apr 27, 2016 at 11:30:59AM -0500, Joel Sherrill wrote: > On Apr 27, 2016 12:31 PM, "printk" wrote: > > > > Hello, I am translating Makefile.am(s) to kbuild > > > > > # > > > # DIRECTORY_SCAN_C_FILES = > > > # ## Newlib SHOULD ha

when the getcwd.c is compiled?

Hello, I am translating Makefile.am(s) to kbuild > # > # DIRECTORY_SCAN_C_FILES = > # ## Newlib SHOULD have provided this one > # DIRECTORY_SCAN_C_FILES += src/readdir_r.c > # ## Comment out when using these from newlib's unix directory > # DIRECTORY_SCAN_C_FILES += src/getcwd.c > # > # ID_C_FIL

start trying to build rtems with kbuild

hi, a11: I am trying to build rtems with kbuild on linux. just a hobby, make rtems easier to build on linux. not support freebsd, windows... (I guess some company don't use windows or linux, securty is critical for them. for small companies, e.g. shenzhen small companies, convenien is more importan

Re: build failed: cpukit/posix/src/conddefaultattributes.c

ou please tell me more about the thread model and SMP saftety? where is the code to read or ? > On Apr 24, 2016 10:14 AM, "printk" wrote: > > > Ah, I works now. thank you all! > > I guess rtems maybe not easy to compile with other > > toolchain. eg. armcc, arm-n

Re: build failed: cpukit/posix/src/conddefaultattributes.c

Ah, I works now. thank you all! I guess rtems maybe not easy to compile with other toolchain. eg. armcc, arm-none-eabi-gcc(ARM: https://launchpad.net/gcc-arm-embedded). ... duhuanpeng. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailm

Re: the rtems kernel source list

pukit in cpukit? :D, just a leaning homework, please kindly corret me. On Fri, Apr 22, 2016 at 01:02:03PM +1000, Chris Johns wrote: > On 22/04/2016 12:19, printk wrote: > >Hello, > >I am learning RTEMS, where is the kernel source, I find some > >place seems holding the ker

Re: build failed: cpukit/posix/src/conddefaultattributes.c

> On Apr 23, 2016 6:50 AM, "printk" wrote: > > Hi, I followed this to build the bsp, arm920 > - - - > be built to target the BOARD_SUPPORT_PACKAGE board. > mkdir build-rtems > cd build-rtems > ../rtems-4.10.0/configure --target=

build failed: cpukit/posix/src/conddefaultattributes.c

Hi, I followed this to build the bsp, arm920 - - - be built to target the BOARD_SUPPORT_PACKAGE board. mkdir build-rtems cd build-rtems ../rtems-4.10.0/configure --target= \ --disable-posix --disable-networking --disable-cxx \ --enable-rtemsbsp=\

arm shared code contains not shared code?

Hello, I am learning the rtems source, and when i look into this folder: rtems@book64:~/rtems-lite/rtems/c/src/lib/libcpu/arm/shared$ tree . ├── arm920 │   └── mmu.c └── include ├── am335x.h ├── arm-cp15.h ├── cache_.h ├── mmu.h ├── omap3.h └── o

the rtems kernel source list

Hello, I am learning RTEMS, where is the kernel source, I find some place seems holding the kernel source: