summaryrefslogtreecommitdiffstats
path: root/c/Makefile.in (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Patch from Eric VALETTE <valette@crf.canon.fr>:Joel Sherrill1998-07-231-1/+13
| | | | | | | | | | | | | Here is a enhanced version of my previous patch. This patch enables to potentially share the new interrupt management code for all Intel targets (pc386, go32 and force386) bsp. Note : this patch is complete only for pc386. It still needs to be completed for go32 and force386. I carrefully checked that anything needed is in for force386 (only some function name changes for IDT manipulation and GDT segment manipulation). But anyway I will not be able to test any of theses targets...
* Added stanzas for debug_tests and profile_tests.Joel Sherrill1998-04-061-0/+6
|
* Changed to remove warning.Joel Sherrill1998-03-031-5/+3
|
* Big patch form Ralf Corsepius described in this email:Joel Sherrill1998-01-301-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here is the result of my nightly work to get RTEMS_ROOT=$srcdir working with different shells and relative/absolute paths. What I did is relatively simple in principle: Instead of setting RTEMS_ROOT in configure.in and then let configure substitute @RTEMS_ROOT@ inside the Makefiles, I now let each Makefile set RTEMS_ROOT from each Makefile's @top_srcdir@ value. The difference is subtile, but with enormous side effects: - If RTEMS_ROOT is set in configure, then the same single value will be propagated to all Makefiles. This breaks using relative paths, as the relative path to the root of the source tree is used inside of all subdirectory Makefiles. - Now each Makefile.in sets RTEMS_ROOT = @top_srcdir@. top_srcdir is computed individually by configure for each single Makefile.in, hereby receiving the correct value, no matter if relative or absolute paths are used. To get this working, I needed to remove setting RTEMS_ROOT from target.cfg.in, because this overrides the value of RTEMS_ROOT from each individual Makefile. Furthermore, I removed RTEMS_CUSTOM from the Makefiles and replaced all "include $(RTEMS_CUSTOM)" directives with"include $(RTEMS_ROOT)/make/custom/$(RTEMS_BSP)". Perhaps you don't like this, but I think, to have one variable less is clearer and easier to understand than having several variables refering to the next one. I enclose a small patch to this mail, which - fixes the config.h problem (to finally clearify misunderstands) - removes assignment/subsitution of RTEMS_ROOT from configure.in - contains a workaround for the application Makefile's RTEMS_ROOT problem (reported by Eric) - removes some unused lines from the toplevel Makefile.in - removes assignment of RTEMS_ROOT from make/target.cfg.in
* Fix from Eric Norum:Joel Sherrill1998-01-271-1/+1
| | | | | There's an explicit invocation of `make' in c/Makefile.in. This breaks for those of us with different `gmake' and `make' programs.
* Removed CONFIG_DIR and PROJECT_HOME directories.Joel Sherrill1998-01-201-15/+11
|
* Modified a lot of files to take a first cut at supporting building fromJoel Sherrill1997-12-101-10/+21
| | | | | any directory in the build tree. The only variable which must be set before the command "gmake" is invoked is RTEMS_BSP (e.g. RTEMS_BSP=erc32).
* Reworked mkdir line to invoke smaller lines.Joel Sherrill1997-12-041-1/+4
|
* Do not generate make/os at install point.Joel Sherrill1997-11-301-2/+1
|
* Moved rtems directory up one directory in the install point. It wasJoel Sherrill1997-10-211-9/+9
| | | | formerly under $(target) and is now at the same level.
* Redid the installation of the "make" directory at the install point.Joel Sherrill1997-10-071-21/+11
| | | | It is no longer a link. It is a copy.
* Fixed bug where include not actually created.Joel Sherrill1997-10-061-2/+5
|
* Added rule so TARGET_VARIANTS are dependent on the environment stuff.Joel Sherrill1997-08-271-1/+4
|
* Added include/motorola and include/zilog directories to theJoel Sherrill1997-08-041-8/+10
| | | | install tree and cleaned up spacing.
* Merged very large and much appreciated patch from Chris JohnsJoel Sherrill1997-07-311-1/+5
| | | | | <cjohns@plessey.com.au>. This patch includes the ods68302 bsp, the RTEMS++ class library, and the rtems++ test.
* added ka9q stackJoel Sherrill1997-05-271-0/+5
|
* KA9Q stack removed prior to testing for 4.0.0 public release.Joel Sherrill1997-05-231-5/+0
|
* Added support for HW API packageJoel Sherrill1997-04-221-10/+2
|
* Added directories to place test output screens into as part of fixingJoel Sherrill1997-04-151-3/+4
| | | | difftest.
* Added ka9q tcpip stack and network driver for the gen68360. This effortJoel Sherrill1997-04-091-1/+6
| | | | | | | | | | | | | was done based on the 3.6.0 release and had to be autoconf'ed locally. It is turned on is the bsp enables it and it is not explicitly disabled via the configure option --disable-tcpip. As many warnings as possible were removed locally after the code was merged. Only the gen68360 and mvme136 bsps were compiled this way. The ka9q port and network driver were submitted by Eric Norum (eric@skatter.USask.Ca). The network demo programs are not included in the tree at this point.
* This set of changes is the build of what was required to convert toJoel Sherrill1997-04-011-0/+98
GNU autoconf. This is the first large step in allowing an RTEMS user to perform a one-tree build (per crossgcc FAQ) including RTEMS in the build process. With this change RTEMS is configured in built in the same style as the GNU tools, yet retains the basic structure of its traditional Makefiles (ala Tony Bennett). Jiri Gaisler (jgais@wd.estec.esa.nl) deserves (and received) a big thank you for doing this. There are still issues to be resolved but as of this commit, all target which can be built on a linux host have been using a modified version of the source Jiri submitted. This source was merged and most targets built in the tree before this commit. There are some issues which remain to be resolved but they are primarily related to host OS dependencies, script issues, the use of gawk for hack_specs, and the dependence on gcc snapshots. These will be resolved.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-19 15:49:12 +0000