Browse Source

- fix missing/incorrect svn file props

git-svn-id: svn://svn.berlios.de/openocd/trunk@1292 b42882b7-edfa-0310-969c-e2dbd0fdcd60
tags/v0.1.0
ntfreak 12 years ago
parent
commit
185870615c
16 changed files with 98 additions and 97 deletions
  1. +0
    -0
      testing/build.test1/Makefile
  2. +0
    -0
      testing/build.test1/Makefile.ftd2xx
  3. +0
    -0
      testing/build.test1/Makefile.libftdi
  4. +0
    -0
      testing/build.test1/Makefile.libusb
  5. +0
    -0
      testing/build.test1/Makefile.openocd
  6. +39
    -38
      testing/build.test1/README.TXT
  7. +0
    -0
      testing/build.test1/local.uses
  8. +0
    -0
      testing/build.test1/mingw32_help/include/elf.h
  9. +0
    -0
      testing/build.test1/mingw32_help/include/sys/cdefs.h
  10. +0
    -0
      testing/build.test1/mingw32_help/include/sys/elf32.h
  11. +0
    -0
      testing/build.test1/mingw32_help/include/sys/elf64.h
  12. +0
    -0
      testing/build.test1/mingw32_help/include/sys/elf_common.h
  13. +0
    -0
      testing/build.test1/mingw32_help/include/sys/elf_generic.h
  14. +0
    -0
      testing/build.test2/Makefile
  15. +59
    -59
      testing/build.test2/README.txt
  16. +0
    -0
      testing/build.test2/local.uses

+ 0
- 0
testing/build.test1/Makefile View File


+ 0
- 0
testing/build.test1/Makefile.ftd2xx View File


+ 0
- 0
testing/build.test1/Makefile.libftdi View File


+ 0
- 0
testing/build.test1/Makefile.libusb View File


+ 0
- 0
testing/build.test1/Makefile.openocd View File


+ 39
- 38
testing/build.test1/README.TXT View File

@@ -1,39 +1,39 @@
Dec 26,2008
---------------------------------------------------------------------------
1) Make a directory some where..
mkdir ~/test
2) Change to that directory
cd ~/test
3) Checkout OpenOCD in that directory.
cd ~/test
svn co https://svn.berlios.de/svnroot/repos/openocd/trunk openocd
4) Copy the "build.test1" directory to the "~/work" directory.
cd ~/test
cp ~/openocd/testing/build.test1/. ~/test/.
5) If needed, download various components.
cd ~/work
make all.download
6) For Linux - type:
cd ~/work
make linux.buildtest
7) For Cygwin - type:
cd ~/work
make cygwin.buildtest
-- Duane Ellis'es test case for building numerous openocd configurations...
Dec 26,2008
---------------------------------------------------------------------------

1) Make a directory some where..

mkdir ~/test

2) Change to that directory

cd ~/test

3) Checkout OpenOCD in that directory.

cd ~/test
svn co https://svn.berlios.de/svnroot/repos/openocd/trunk openocd

4) Copy the "build.test1" directory to the "~/work" directory.


cd ~/test
cp ~/openocd/testing/build.test1/. ~/test/.

5) If needed, download various components.

cd ~/work
make all.download


6) For Linux - type:

cd ~/work
make linux.buildtest

7) For Cygwin - type:

cd ~/work
make cygwin.buildtest


+ 0
- 0
testing/build.test1/local.uses View File


+ 0
- 0
testing/build.test1/mingw32_help/include/elf.h View File


+ 0
- 0
testing/build.test1/mingw32_help/include/sys/cdefs.h View File


+ 0
- 0
testing/build.test1/mingw32_help/include/sys/elf32.h View File


+ 0
- 0
testing/build.test1/mingw32_help/include/sys/elf64.h View File


+ 0
- 0
testing/build.test1/mingw32_help/include/sys/elf_common.h View File


+ 0
- 0
testing/build.test1/mingw32_help/include/sys/elf_generic.h View File


+ 0
- 0
testing/build.test2/Makefile View File


+ 59
- 59
testing/build.test2/README.txt View File

@@ -1,59 +1,59 @@
This makefile is how I Duane Ellis (openocd@duaneellis.com) builds
openocd test purposes on Cygwin. I have included it here so others
might also make use of the same configuration that I use to develop
Openocd.
--Duane Ellis
To make use of it do the following:
(1) Check out openocd in the standard way.
For example - in cygwin, type this:
bash$ mkdir -p /home/duane/test
bash$ cd /home/duane/test
bash$ svn co https://svn.berlios.de/svnroot/repos/openocd/trunk openocd
(2) COPY this folder "right above" where you have OpenOCD.
bash$ cd /home/duane/test
bash$ cp ./openocd/testing/build.test2/* /home/duane/test/.
(3) OPTIONALLY
You might want to review the file "local.uses"
Change options and so forth at the top of the file.
(4) Initially, you need to download some additional files.
These include "libftdi", "libconfuse", and the ftd2xx drivers.
(5) You also need to build the supporting libraries and install them
(They are installed "locally" only)
Type this command:
bash$ cd /home/duane/test
bash$ make initial.build
which: (1) downloads files
(2) builds the libs
(3) builds OpenOCD
(6) As you hack upon OpenOCD... to rebuild OpenOCD...
bash$ cd /home/duane/test
bash$ make remake
which: (1) re-bootstraps
(2) re-configures
(3) re-builds
(4) re-installs.
=======
**END**
=======
This makefile is how I Duane Ellis (openocd@duaneellis.com) builds
openocd test purposes on Cygwin. I have included it here so others
might also make use of the same configuration that I use to develop
Openocd.
--Duane Ellis
To make use of it do the following:
(1) Check out openocd in the standard way.
For example - in cygwin, type this:
bash$ mkdir -p /home/duane/test
bash$ cd /home/duane/test
bash$ svn co https://svn.berlios.de/svnroot/repos/openocd/trunk openocd
(2) COPY this folder "right above" where you have OpenOCD.
bash$ cd /home/duane/test
bash$ cp ./openocd/testing/build.test2/* /home/duane/test/.
(3) OPTIONALLY
You might want to review the file "local.uses"
Change options and so forth at the top of the file.
(4) Initially, you need to download some additional files.
These include "libftdi", "libconfuse", and the ftd2xx drivers.
(5) You also need to build the supporting libraries and install them
(They are installed "locally" only)
Type this command:
bash$ cd /home/duane/test
bash$ make initial.build
which: (1) downloads files
(2) builds the libs
(3) builds OpenOCD
(6) As you hack upon OpenOCD... to rebuild OpenOCD...
bash$ cd /home/duane/test
bash$ make remake
which: (1) re-bootstraps
(2) re-configures
(3) re-builds
(4) re-installs.
=======
**END**
=======

+ 0
- 0
testing/build.test2/local.uses View File


Loading…
Cancel
Save