Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Z
zmap
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
zmap
Commits
84000d88
Commit
84000d88
authored
15 years ago
by
edgrif
Browse files
Options
Downloads
Patches
Plain Diff
replaced.
parent
935111ab
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
foocanvas/README
+0
-70
0 additions, 70 deletions
foocanvas/README
with
0 additions
and
70 deletions
foocanvas/README
deleted
100755 → 0
+
0
−
70
View file @
935111ab
================================================================================
foocanvas directory
================================================================================
This directory contains the files used to construct our version of the
foocanvas. This is not straight forward because we have:
- modified the foocanvas code itself
- created our own additional files which must be added to the foocanvas code
- modified the build scripts to get our files included in the build
We have elected to do this by:
- checking out the latest copy of the foocanvas from the copy at the gnome site
- copying our files into this copy
- applying our changes to the foocanvas source and build files as a patch
Because this is not completely simple there are two scripts in this directory
to do this. These scripts MUST BE RUN from within this directory.
The scripts run as a pair:
make_working_foocanvas
----------------------
This script produces a subdirectory called FOOCANVAS-WORKING-COPY. This
subdirectory contains the latest source for foocanvas in foocanvas.latest, the
patch file to convert this copy into our version of foocanvas as
libfoocanvas-XXXXX.patch, and a merged working copy of our version of foocanvas
in foocanvas.working. This merged version can be used both to do a build and
for making changes.
To do the build cd to foocanvas.working and type:
autogen.sh --prefix=<directory where you will want to install foocanvas>
when that has finished you can simply type 'make' and 'make install'
Alternatively if you simply want to do a build with the current patch and the
version of foocanvas that the patch was created from (stored in cvs with the
patch) then you use the -b flag:
make_working_foocanvas -b
This produces the same directory structure as before and you run autogen.sh as
before.
make_cvs_foocanvas
------------------
When you have finished altering the code you can run make_cvs_foocanvas to
prepare the files that need to go into cvs and you can optionally have them
checked back in by the script. If you decide to check them back in yourself
you should look in the script to check the -kN options that are required for
the files to go back into cvs in the correct format.
To prepare the files, check them back in to cvs and also remove the working
directory:
make_cvs_foocanvas -c"description used by script to do cvs commit" -r
and that should be it.
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment