Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
a7e96ed4
Commit
a7e96ed4
authored
24 years ago
by
Mark Wielaard
Committed by
Mark Wielaard
24 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* HACKING: new file
From-SVN: r39799
parent
f74fd2bb
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
50 additions
and
0 deletions
+50
-0
libjava/ChangeLog
+4
-0
libjava/HACKING
+46
-0
No files found.
libjava/ChangeLog
View file @
a7e96ed4
2001-02-17 Mark Wielaard <mark@klomp.org>
* HACKING: new file
2001-02-17 Mark Wielaard <mark@klomp.org>
* java/io/DataInputStream.java: update copyright notice
* java/io/PrintWriter.java: idem
* java/io/Reader.java: idem
...
...
This diff is collapsed.
Click to expand it.
libjava/HACKING
0 → 100644
View file @
a7e96ed4
Things libgcj hackers should know
---------------------------------
If you want to hack on the libgcj files you need to be aware of the
following things. There are probably lots of other things that should be
explained in this HACKING file. Please add them if you discover them :)
--
A lot of the standard library files come from the GNU Classpath project.
<http://www.gnu.org/software/classpath/>
The libgcj and Classpath project have officially merged, but the merge
is not yet complete. Our eventual goal is for Classpath to be an upstream
source provider for libgcj, however it will be some time before this becomes
reality: libgcj and Classpath have different implementations of many core
java classes. In order to merge them, we need to select the best (most
efficient, cleanest) implementation of each method/class/package, resolve
any conflicts created by the merge, and test the final result.
The merged files can be recognized by the standard Classpath copyright
comments at the top of the file. If you make changes to these files then
you should also send a patch to the classpath mailinglist.
<http://mail.gnu.org/mailman/listinfo/classpath/>
<mailto:classpath@gnu.org>
If you merge a libgcj class with a classpath class then you must update the
copyright notice at the top of the file so others can see that this is a
shared libgcj/classpath file.
--
If you need to add new java files to libgcj then you have to edit the
Makefile.am file in the top (libjava) directory. And run automake.
But note the following (thanks to Bryce McKinlay):
> Do you know the magic dance I have to do when adding files to Makefile.am
> so they will appear in Makefile.in and finally in the user generated
> Makefile?
Yup, you need the magic libgcj automake ;-)
<ftp://ftp.freesoftware.com/.0/sourceware/java/automake-gcj-1.4.tar.gz>
Install that (dont worry, it should still work for other projects), add your
files to the Makefile.am, then just type "automake" and it will regenerate the
Makefile.in. Easy!
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment