Skip to content

Commit 5260fa8

Browse files
author
Paul Gorlinsky
committed
Change to LF (UNIX style) line terminator
git-svn-id: file:///home/jj/hercules.svn/trunk@6116 956126f8-22a0-4046-8f4a-272fa8102e63
1 parent bf0b823 commit 5260fa8

File tree

10 files changed

+3494
-3494
lines changed

10 files changed

+3494
-3494
lines changed

‎README.AIX

Lines changed: 49 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,49 +1,49 @@
1-
-------------------------------------------------------------------------------
2-
3-
4-
*** PRELIMINARY ***
5-
6-
7-
Building Hercules-390 for AIX 5.3
8-
------------------------------------
9-
10-
11-
1. Standard AIX systems do not have autoconf, automake, zlib
12-
or bzip2 libraries and headers; these can be downloaded
13-
from <http://www.oss4aix.org/download/latest/aix53/> and
14-
installed using rpm (rpm is part of AIX 5.3).
15-
16-
Autoconf/automake require some pre-requisites, such as gettext,
17-
info, m4, libsigsegv and expat; all these could be downloaded
18-
and installed from the same place.
19-
20-
21-
2. Enter the configure and make commands to build/install Hercules:
22-
23-
./configure && make && make install
24-
25-
(or you can run each command separately if you want).
26-
27-
28-
3. That's it! Enjoy your private mainframe. :)
29-
30-
31-
-------------------------------------------------------------------------------
32-
33-
The above is based on efforts done by Alexey Bozrikov [[email protected]],
34-
Harold Grovesteen [[email protected]] and Fish [[email protected]]
35-
on the Hercules-390 Yahoo group list during the month of October 2009.
36-
37-
-------------------------------------------------------------------------------
38-
39-
40-
Still remaining TODO:
41-
42-
- Get SCSI tape working: resolve <sys/mtio.h> header & 'struct mtget' issue(s).
43-
44-
#if defined( HAVE_STRUCT_MTGET_MT_GSTAT )
45-
#else // !defined( HAVE_STRUCT_MTGET_MT_GSTAT )
46-
#endif // defined( HAVE_STRUCT_MTGET_MT_GSTAT )
47-
48-
- Test networking (did you do this yet Alexey?)
49-
1+
-------------------------------------------------------------------------------
2+
3+
4+
*** PRELIMINARY ***
5+
6+
7+
Building Hercules-390 for AIX 5.3
8+
------------------------------------
9+
10+
11+
1. Standard AIX systems do not have autoconf, automake, zlib
12+
or bzip2 libraries and headers; these can be downloaded
13+
from <http://www.oss4aix.org/download/latest/aix53/> and
14+
installed using rpm (rpm is part of AIX 5.3).
15+
16+
Autoconf/automake require some pre-requisites, such as gettext,
17+
info, m4, libsigsegv and expat; all these could be downloaded
18+
and installed from the same place.
19+
20+
21+
2. Enter the configure and make commands to build/install Hercules:
22+
23+
./configure && make && make install
24+
25+
(or you can run each command separately if you want).
26+
27+
28+
3. That's it! Enjoy your private mainframe. :)
29+
30+
31+
-------------------------------------------------------------------------------
32+
33+
The above is based on efforts done by Alexey Bozrikov [[email protected]],
34+
Harold Grovesteen [[email protected]] and Fish [[email protected]]
35+
on the Hercules-390 Yahoo group list during the month of October 2009.
36+
37+
-------------------------------------------------------------------------------
38+
39+
40+
Still remaining TODO:
41+
42+
- Get SCSI tape working: resolve <sys/mtio.h> header & 'struct mtget' issue(s).
43+
44+
#if defined( HAVE_STRUCT_MTGET_MT_GSTAT )
45+
#else // !defined( HAVE_STRUCT_MTGET_MT_GSTAT )
46+
#endif // defined( HAVE_STRUCT_MTGET_MT_GSTAT )
47+
48+
- Test networking (did you do this yet Alexey?)
49+

‎README.DYNMOD

Lines changed: 125 additions & 125 deletions
Original file line numberDiff line numberDiff line change
@@ -1,125 +1,125 @@
1-
-------------------------------------------------------------------------------
2-
3-
Hercules Dynamic Modules
4-
5-
(on Windows)
6-
7-
-------------------------------------------------------------------------------
8-
9-
Required Files
10-
11-
12-
Required files:
13-
14-
makefile: "{modname}.msvc" defines module name and source file(s)
15-
resource file: "{modname}.rc" the module's version resource file
16-
17-
-------------------------------------------------------------------------------
18-
19-
makefile stub format
20-
21-
22-
Required makefile format:
23-
24-
# Module name:
25-
26-
DYNMOD = {modname}
27-
28-
# Source files:
29-
30-
DYNOBJ = \
31-
$(O){srcfile1}.obj \
32-
$(O){srcfile2}.obj \
33-
$(O){srcfile3}.obj
34-
... etc...
35-
36-
Your makefile is !INCLUDEd as part of Hercules's main makefile and
37-
thus your dynamic module gets built along with the rest of Hercules.
38-
39-
-------------------------------------------------------------------------------
40-
41-
The MAKE/BUILD command
42-
43-
44-
Building (making):
45-
46-
47-
dynmake.bat {projdir} {modname} {build_type} {num_cpus} [-a|clean]
48-
49-
e.g.:
50-
51-
"X:\Hercules\dynmake.bat" "$(SolutionDir)" {modname} RETAIL 32 -a
52-
53-
54-
The {projdir} value you pass MUST be a fully qualified path to your
55-
dynamic module's project directory where all of your files are. The
56-
dynamke.bat command you invoke should also be a fully qualifed path
57-
to the desired Hercules dynmake.bat file. The other arguments (i.e.
58-
{build_type}, {num_cpus}, etc) are identical to the values normally
59-
specified for the main Hercules "makefile.bat" command used to build
60-
Hercules with. Refer to makefile.bat for details.
61-
62-
-------------------------------------------------------------------------------
63-
64-
Pre-Build event and Post-Build event callbacks
65-
66-
67-
Optional files:
68-
69-
prebuild.bat Called before the main Hercules makefile.bat is called.
70-
postbld.bat Called after the main Hercules makefile.bat is called.
71-
72-
During the build process, dynmake.bat checks if the file exists in your
73-
specified project directory and if it does, calls it with the following
74-
parameters:
75-
76-
{hercdir} {modname} {build_type} {num_cpus} [-a|clean]
77-
78-
The {hercdir} value is the fully qualified path the main Hercules source
79-
code directory. The other parameters are the same values that you passed
80-
to the dynmake.bat command.
81-
82-
-------------------------------------------------------------------------------
83-
84-
Resource Compiler
85-
86-
87-
For your convenience the following #defines are also passed to the resource
88-
compiler on the command-line during the actual build process:
89-
90-
VERSION The Hercules version string (e.g. "3.06-svn-5602")
91-
TARGETFILENAME Your module name string (e.g. "{modname}.dll")
92-
MAX_CPU_ENGINES_STR Number of CPUs as a string (e.g. "32")
93-
94-
Use them in your .rc resource file's VERSIONINFO structure as needed.
95-
96-
-------------------------------------------------------------------------------
97-
98-
The Build Process
99-
100-
101-
Dynmake.bat first creates a work subdirectory beneath Hercules's main source
102-
code directory using the same name as the {modname} you passed to it.
103-
104-
It then calls your prebuild.bat file if it exists. Use this callback to
105-
perform any pre-build adjustments to your source files that may be necessary
106-
before the actual build process begins.
107-
108-
When your prebuild.bat returns, it then copys all *.c, *.h, *.rc, *.rc2 and
109-
*.msvc files from your project directory into its {modname} subdirectory and
110-
invokes Hercules's primary "makefile.bat" script to perform the actual build.
111-
112-
When the build is done it then calls your postbld.bat callback if it exists.
113-
You can use this callback to copy the resulting binary from Hercules's output
114-
directory to your project directory or whatever other post-build processing
115-
your product may require.
116-
117-
-------------------------------------------------------------------------------
118-
119-
More Information
120-
121-
122-
For additional information regarding dynamic modules please see the "Hercules
123-
Dynamic Loader" readme document called "README.HDL".
124-
125-
-------------------------------------------------------------------------------
1+
-------------------------------------------------------------------------------
2+
3+
Hercules Dynamic Modules
4+
5+
(on Windows)
6+
7+
-------------------------------------------------------------------------------
8+
9+
Required Files
10+
11+
12+
Required files:
13+
14+
makefile: "{modname}.msvc" defines module name and source file(s)
15+
resource file: "{modname}.rc" the module's version resource file
16+
17+
-------------------------------------------------------------------------------
18+
19+
makefile stub format
20+
21+
22+
Required makefile format:
23+
24+
# Module name:
25+
26+
DYNMOD = {modname}
27+
28+
# Source files:
29+
30+
DYNOBJ = \
31+
$(O){srcfile1}.obj \
32+
$(O){srcfile2}.obj \
33+
$(O){srcfile3}.obj
34+
... etc...
35+
36+
Your makefile is !INCLUDEd as part of Hercules's main makefile and
37+
thus your dynamic module gets built along with the rest of Hercules.
38+
39+
-------------------------------------------------------------------------------
40+
41+
The MAKE/BUILD command
42+
43+
44+
Building (making):
45+
46+
47+
dynmake.bat {projdir} {modname} {build_type} {num_cpus} [-a|clean]
48+
49+
e.g.:
50+
51+
"X:\Hercules\dynmake.bat" "$(SolutionDir)" {modname} RETAIL 32 -a
52+
53+
54+
The {projdir} value you pass MUST be a fully qualified path to your
55+
dynamic module's project directory where all of your files are. The
56+
dynamke.bat command you invoke should also be a fully qualifed path
57+
to the desired Hercules dynmake.bat file. The other arguments (i.e.
58+
{build_type}, {num_cpus}, etc) are identical to the values normally
59+
specified for the main Hercules "makefile.bat" command used to build
60+
Hercules with. Refer to makefile.bat for details.
61+
62+
-------------------------------------------------------------------------------
63+
64+
Pre-Build event and Post-Build event callbacks
65+
66+
67+
Optional files:
68+
69+
prebuild.bat Called before the main Hercules makefile.bat is called.
70+
postbld.bat Called after the main Hercules makefile.bat is called.
71+
72+
During the build process, dynmake.bat checks if the file exists in your
73+
specified project directory and if it does, calls it with the following
74+
parameters:
75+
76+
{hercdir} {modname} {build_type} {num_cpus} [-a|clean]
77+
78+
The {hercdir} value is the fully qualified path the main Hercules source
79+
code directory. The other parameters are the same values that you passed
80+
to the dynmake.bat command.
81+
82+
-------------------------------------------------------------------------------
83+
84+
Resource Compiler
85+
86+
87+
For your convenience the following #defines are also passed to the resource
88+
compiler on the command-line during the actual build process:
89+
90+
VERSION The Hercules version string (e.g. "3.06-svn-5602")
91+
TARGETFILENAME Your module name string (e.g. "{modname}.dll")
92+
MAX_CPU_ENGINES_STR Number of CPUs as a string (e.g. "32")
93+
94+
Use them in your .rc resource file's VERSIONINFO structure as needed.
95+
96+
-------------------------------------------------------------------------------
97+
98+
The Build Process
99+
100+
101+
Dynmake.bat first creates a work subdirectory beneath Hercules's main source
102+
code directory using the same name as the {modname} you passed to it.
103+
104+
It then calls your prebuild.bat file if it exists. Use this callback to
105+
perform any pre-build adjustments to your source files that may be necessary
106+
before the actual build process begins.
107+
108+
When your prebuild.bat returns, it then copys all *.c, *.h, *.rc, *.rc2 and
109+
*.msvc files from your project directory into its {modname} subdirectory and
110+
invokes Hercules's primary "makefile.bat" script to perform the actual build.
111+
112+
When the build is done it then calls your postbld.bat callback if it exists.
113+
You can use this callback to copy the resulting binary from Hercules's output
114+
directory to your project directory or whatever other post-build processing
115+
your product may require.
116+
117+
-------------------------------------------------------------------------------
118+
119+
More Information
120+
121+
122+
For additional information regarding dynamic modules please see the "Hercules
123+
Dynamic Loader" readme document called "README.HDL".
124+
125+
-------------------------------------------------------------------------------

0 commit comments

Comments
 (0)