• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

README_FILES/H02-Feb-2019-787677

data/H03-May-2022-1,2801,109

doc/H07-May-2022-29,35225,340

example/H02-Feb-2019-5,2705,004

gts/H03-May-2022-31,41622,020

intl/H02-Feb-2019-27,14319,784

lib/H03-May-2022-99,90795,382

m4/H02-Feb-2019-4,8914,592

newlib/H02-Feb-2019-9,3208,444

po/H02-Feb-2019-35,14727,889

src/H03-May-2022-173,382124,869

tests/H03-May-2022-81,21479,049

tools/H03-May-2022-1,4471,129

tutorial/H02-Feb-2019-2,5602,441

w32/H02-Feb-2019-6,5425,393

win32/H03-May-2022-4,1543,298

ABOUT-NLSH A D15-Jan-201791.6 KiB1,2831,244

AUTHORSH A D16-Nov-2011297 76

COPYINGH A D10-Jan-201917.6 KiB341281

ChangeLogH A D01-Feb-20191.1 MiB25,84617,556

INSTALLH A D12-Sep-201510.2 KiB261194

Makefile.amH A D27-Jan-2019734 209

Makefile.inH A D03-May-202226.8 KiB857770

NEWSH A D01-Feb-201968.6 KiB1,8731,523

READMEH A D12-Sep-2015831 2718

README.gitH A D12-Sep-20154.1 KiB13696

README.w32H A D10-Jan-20191,004 3321

README.win32H A D27-Jan-20191.3 KiB5033

acinclude.m4H A D12-Sep-201515.4 KiB470441

aclocal.m4H A D01-Feb-201950.7 KiB1,3941,255

compileH A D16-Nov-20113.6 KiB14379

config.guessH A D10-Jan-201942.4 KiB1,4391,246

config.h.inH A D01-Feb-201923.3 KiB767563

config.rpathH A D15-Jan-201718.1 KiB685588

config.subH A D10-Jan-201935.2 KiB1,8111,673

configureH A D01-Feb-2019604.9 KiB21,28817,640

configure.acH A D01-Feb-201939.7 KiB1,3741,190

depcompH A D16-Nov-201115.5 KiB530329

globalconst.hH A D27-Jan-20195.1 KiB14171

icon-theme-installerH A D16-Nov-20115.3 KiB18492

install-shH A D16-Nov-20119 KiB324189

missingH A D27-Aug-20176.7 KiB216143

mkinstalldirsH A D07-Sep-20111.9 KiB11285

ylwrapH A D16-Nov-20116 KiB223124

README

1Pcb is a CAD (computer aided design) program for the physical
2design of printed circuit boards.
3
4For installing the release refer to the file 'INSTALL'.
5For additional information read the manual (doc/pcb.pdf)
6
7If you are updating to a new snapshot, you may wish to read
8the ChangeLog file.  People using git are expected to look
9at the git commit messages, instead.
10
11There is also a bug tracking system available which can
12be found from http://pcb.geda-project.org.
13
14
15-------------------------------------------------------------------------
16                            COPYRIGHT
17
18PCB is covered by the GNU General Public License.  See the individual
19files for the exact copyright notices.
20
21  Contact addresses for paper mail and Email:
22  harry eaton
23  6697 Buttonhole Court
24  Columbia, MD 21044
25  haceaton@aplcomm.jhuapl.edu
26
27

README.git

1=======================
2 Building PCB from git
3=======================
4
5This file describes how to build from git sources.  If you are
6building from a released version or snapshot, please refer to the
7'INSTALL' document instead.  Take the time to read this file, it's not
8that long and it addresses some questions which come up with some
9frequency.
10
11-------------
12Prerequisites
13-------------
14
15You will need the following tools to obtain and build a git version of
16PCB:
17
18git       -- To download and track sources you will need the 'git'
19             version control tool installed.
20
21To compile you will need a C compiler (such as 'gcc'), a 'lex' (or
22'flex') and a 'yacc' (or 'bison') implementation.  If you do not have
23'lex' or 'yacc', try installing:
24
25bison     -- ftp://ftp.gnu.org/pub/gnu/bison/
26flex      -- ftp://ftp.gnu.org/pub/non-gnu/flex/
27
28In addition you will need recent versions of:
29
30autoconf  -- ftp://ftp.gnu.org/pub/gnu/autoconf/
31             Please note that version 2.13 is too old.  Current development
32             is done with 2.59.
33
34automake  -- ftp://ftp.gnu.org/pub/gnu/automake/
35             The developers use the 1.9.* versions of automake.  Older
36             versions have not been as well tested (or tested at all).
37             Versions 1.7 and older are too old and will not work.
38
39gettext   -- ftp://ftp.gnu.org/pub/gnu/gettext/
40             You will need version 0.14.x, or 0.16.x or higher
41
42intltool  -- https://edge.launchpad.net/intltool/+download
43             You will need version 0.35.0 or higher
44
45texinfo   -- ftp://ftp.gnu.org/pub/gnu/texinfo/
46             You will need at least version 4.6 to be able to build
47             the documentation.
48
49perl      -- Version 5 or newer.  This is needed for building the
50             documentation.
51
52latex     -- This is needed for building the documentation.
53
54You can find the version of autoconf, automake, and makeinfo by
55running them with the '--version' flag.
56
57If you do not wish to build the documentation, use '--disable-doc'
58when you run configure.  When building from a release tarball, the
59documentation comes preformatted.
60
61------------------------
62Clone the PCB repository
63------------------------
64
65If you have previously cloned the PCB source tree, please proceed to
66the updating section.
67
68To clone the PCB repository to your computer, run:
69
70  git clone git://git.geda-project.org/pcb.git
71
72This will download the entire version control history for PCB to
73your computer, and will take some time.
74
75--------
76Updating
77--------
78
79To update your git repository with the latest changes, simply run:
80
81  git pull
82
83----------------------------------
84Bootstrapping with the auto* tools
85----------------------------------
86To create the configure script and the Makefile.in's
87you will need to run:
88
89  ./autogen.sh
90
91from the top level PCB directory.  This will run various programs
92from the GNU autotools to create the 'configure' script, the
93'config.h.in' file and the various 'Makefile.in's.
94
95At this point you can proceed to configure and build PCB as outlined
96in the 'INSTALL' document.
97
98-------------------
99Building a Snapshot
100-------------------
101
102The file 'README.snapshots' documents what is currently done to create
103a snapshot release for PCB.  Most of what is in there has to do with
104the cvs repository and how we tag and branch the sources.  If you are
105interested in building your own .tar.gz file from git sources, you can
106still use the information in 'README.snapshots' as a guide.
107
108------------------
109Advanced git usage
110------------------
111
112If you wish to use git to track your own changes to PCB, use git to
113contribute patches back to the community, or gain 'push' permissions
114for the PCB git repository, please see the gEDA wiki for more
115information:
116
117  http://wiki.geda-project.org/geda:scm
118
119------------------------
120Using CVS instead of git
121------------------------
122
123It is still possible to use CVS to access the PCB sources.  You can
124checkout the latest version using the command:
125
126  cvs -z3 -d:pserver:anonymous@git.geda-project.org/home/git/pcb.git co master
127
128And update them using:
129
130  cvs -z3 update -PdA
131
132..
133        Local Variables:
134        mode: rst
135        End:
136

README.w32

1Building PCB for Windows with a MinGW cross-compiler
2
31) Install a MinGW cross-compiler.
4On Debian and derivatives, you can type 'sudo apt-get install mingw32.'.
5You can also build your own by using the build script provided by the
6MinGW project.
7
8On NetBSD use the cross/mingw package.
9
102) Install native (non-cross) dependencies.
11
12* autoconf
13* automake
14* libtool, gettext, intltool.
15* glib and gtk+.
16* wget (used for fetching tarballs)
17* wine (the tiff build fails without it)
18
193) Edit the w32/minipack.conf file to suit your compiler setup.
20   FIXME -- can we make this take arguments?
21
224) Copy the pcb tarball to w32/sources
23
245) Enter the w32 directory and run ./build_all.
25
266) Wait while the script fetches and compiles the PCB dependencies and PCB itself.
27
287) Run the result with wine: wine result/bin/pcb.exe
29   [NOTE:  This didn't work for me but copying everything to an actual windows machine worked]
30
318) Copy the result directory to a Windows installation (packaging script is not supplied).
32
33

README.win32

1These are instructions on building a windows installer under cygwin but
2with mingw toolchain and libraries.  The result is an install which
3does not depend on cygwin.
4
5If you are looking for instructions on cross-compiling from linux
6or other systems, then refer to README.w32
7
8---------------------------------------------------------------------
9
10These instructions were written based on cygwin64.  When you install
11cygwin64 on your system, you will need to ensure that you have installed:
12
13- autoconf
14- automake
15- bash
16- bison
17- flex
18- gawk
19- intltool
20- make
21- m4
22- sed
23
24In addition, you will need the mingw cross compilation packages.  At the
25time of writing this, the the list of packages installed which have
26been shown to work is contained in win32/mings_required_pkgs.  That
27list was obtained via:
28
29$ cygcheck -c | grep mingw
30
31In addition I have:
32w32api-headers                        4.0.4-1                      OK
33w32api-runtime                        4.0.4-1                      OK
34
35
36Once these have all been installed then when building from a tarball,
37extract, cd win32 and run
38
39./build_pcb
40
41This will create a windows installer.
42
43If you are building from git you will need additional tools to build
44the documentation which can be skipped using
45
46./build_pcb --disable-doc
47
48
49
50