Discussion:
Need a new release of OW
(too old to reply)
Leif Ekblad
2013-06-18 22:03:35 UTC
Permalink
Raw Message
Our company will be involved in a large project after this summer, which
means there will be several people working with OW for RDOS. My problem is
that I don't want to tell them that they need to build the compiler from
source (on a 32-bit machine), rather I want to give them an installation
package (for Windows) that installs a working version of OW for RDOS. They
cannot use the 1.9 release since there have been changes made since then,
and the C-based device drivers won't build because there is still a
"pending" change in clib that I cannot commit (as per a previous post).

I'm trying to build the complete OW source (on WinXP), but it appears the
documentation will not build (missing pdf and html help files).

As I understand it, running makeOW under openwatcom/docs/admin should build
everything needed to create the installation packages, but I cannot make it
work.

Error messages: (in openwatcom\docs)
"Can not open source directory 'htmlhelp/*.chi' : No such file or directory
"Can not open source directory 'htmlhelp/*.chm' : No such file or directory
"Can not open source directory 'pdf/*.pdf' : No such file or directory

Obviously these directories are not built as the only content is "makefile".

What is wrong? What is the time schedule for the next release?

Leif Ekblad
Marty Stanquist
2013-06-19 00:15:04 UTC
Permalink
Raw Message
"Leif Ekblad" wrote in message news:kpqlf7$cmo$***@www.openwatcom.org...

Our company will be involved in a large project after this summer, which
means there will be several people working with OW for RDOS. My problem is
that I don't want to tell them that they need to build the compiler from
source (on a 32-bit machine), rather I want to give them an installation
package (for Windows) that installs a working version of OW for RDOS. They
cannot use the 1.9 release since there have been changes made since then,
and the C-based device drivers won't build because there is still a
"pending" change in clib that I cannot commit (as per a previous post).

I'm trying to build the complete OW source (on WinXP), but it appears the
documentation will not build (missing pdf and html help files).

As I understand it, running makeOW under openwatcom/docs/admin should build
everything needed to create the installation packages, but I cannot make it
work.

Error messages: (in openwatcom\docs)
"Can not open source directory 'htmlhelp/*.chi' : No such file or directory
"Can not open source directory 'htmlhelp/*.chm' : No such file or directory
"Can not open source directory 'pdf/*.pdf' : No such file or directory

Obviously these directories are not built as the only content is "makefile".

What is wrong? What is the time schedule for the next release?

Leif Ekblad

Right. We're planning on doing an intermediate release containing your RDOS
C compiler fix and Michal's Windows-7 fixes only, calling this version 1.91
or 1.9a. This will be built using a 32-bit Windows-7 client and will require
P4V to accomplish some of the release steps. P4V will require an upgrade to
the Perforce server. I have a test machine that I want to configure with the
latest Perforce server and do some test builds with. I'll need to test the
Windows-7 and eCS platforms to make sure they can still access Perforce. If
this goes well, I can go ahead and upgrade the real OW Perforce server and
do the release. I'll try to make more progress on this so you can remain on
schedule.

Marty
Paul S. Person
2013-06-19 16:42:45 UTC
Permalink
Raw Message
Post by Leif Ekblad
Our company will be involved in a large project after this summer, which
means there will be several people working with OW for RDOS. My problem is
that I don't want to tell them that they need to build the compiler from
source (on a 32-bit machine), rather I want to give them an installation
package (for Windows) that installs a working version of OW for RDOS. They
cannot use the 1.9 release since there have been changes made since then,
and the C-based device drivers won't build because there is still a
"pending" change in clib that I cannot commit (as per a previous post).
I'm trying to build the complete OW source (on WinXP), but it appears the
documentation will not build (missing pdf and html help files).
As I understand it, running makeOW under openwatcom/docs/admin should build
everything needed to create the installation packages, but I cannot make it
work.
Error messages: (in openwatcom\docs)
"Can not open source directory 'htmlhelp/*.chi' : No such file or directory
"Can not open source directory 'htmlhelp/*.chm' : No such file or directory
"Can not open source directory 'pdf/*.pdf' : No such file or directory
Obviously these directories are not built as the only content is "makefile".
What is wrong? What is the time schedule for the next release?
Examination of MakeOW.bat shows that it builds OW in the repository.
Or, at least, it is supposed to do so.

I've never used it. And it isn't mentioned in "making-release.txt", so
it apparently is not part of building a release.

I /have/, however, successfully rebuilt OW after a "builder clean" by
going to the root directory ("ow" in my setup, apparently "openwatcom"
in yours) and invoking "build". This runs (under Windows 7 Starter)
build.cmd, which actually does build everything. Well, on my Netbook
here, anyway. (I do this when the normal incremental build fails,
every few months.)

Presumably, you would then copy rel2 and use it as an OW installation.

I found the "source directories" odd, since I know that PS is the
source for PDF, but I suppose that, if the finished files are to be
copied into rel2, then these would be source directories for the
finished help files to be copied.

There is a flag that controls whether or not builder builds the docs;
perhaps you have it set so that they are not built. Changing this
might help. I found it in my setvars.bat (which should be a copy of a
cmd/bat/whatever file in the OW repository root directory):

REM Set this variable to 0 to suppress documentation build
set DOC_BUILD=1

But you probably want it set to 0 if you are using a 64-bit computer.

If you go into each directory and type "wmake", that should build the
docs. They would then be present the next time you try to build -- at
least, they should be if you don't do "builder clean" in the meantime,
and possibly even then. In most directories, however, this may not
work so well if you are using a 64-bit computer, as wgml is a DOS
(extended DOS, perhaps, but 16-bit nonetheless) program, unless you
can run the 32-bit OS/2 version.

However, even on a 64-bit system, with the proper help compilers and
makefiles, it should be possible to create the HTMLHELP and PDF files,
as neither should involve wgml, provided the PS files and whatever
HTMLHELP needs are already present.
--
"Nature must be explained in
her own terms through
the experience of our senses."
Frank Beythien
2013-06-20 08:57:01 UTC
Permalink
Raw Message
Post by Leif Ekblad
Our company will be involved in a large project after this summer, which
means there will be several people working with OW for RDOS. My problem is
that I don't want to tell them that they need to build the compiler from
source (on a 32-bit machine), rather I want to give them an installation
package (for Windows) that installs a working version of OW for RDOS. They
cannot use the 1.9 release since there have been changes made since then,
and the C-based device drivers won't build because there is still a
"pending" change in clib that I cannot commit (as per a previous post).
I'm trying to build the complete OW source (on WinXP), but it appears the
documentation will not build (missing pdf and html help files).
For pdf files you need ghostscript installed and point the build process
to use it.
Post by Leif Ekblad
As I understand it, running makeOW under openwatcom/docs/admin should build
everything needed to create the installation packages, but I cannot make it
work.
Never used makeow.bat, as I use OS/2 eCS for building. And I stick to
8.3 file/directory names. I'm not sure all OW tools can handle longer
names and it can help not exceeding the maximum length of the cmdline or
Path environment variable.
Post by Leif Ekblad
Error messages: (in openwatcom\docs)
"Can not open source directory 'htmlhelp/*.chi' : No such file or directory
"Can not open source directory 'htmlhelp/*.chm' : No such file or directory
"Can not open source directory 'pdf/*.pdf' : No such file or directory
Obviously these directories are not built as the only content is "makefile".
For building OW I use either OW\build.cmd with customized setvars.cmd
(myvars.cmd) or the build server from ow\bld\build\server. But this
requires more setup (perl). Obviously I can't build the Win help files
as I know no OS/2 program to generate chm or chi files.

CU/2
Frank
Paul S. Person
2013-06-21 16:37:23 UTC
Permalink
Raw Message
Post by Frank Beythien
For pdf files you need ghostscript installed and point the build process
to use it.
There's also an hmtlhelp compiler, with corresponding environment
variable, requiring installation, IIRC.

Perhaps this is a flaw in the build process:

if the appropriate help compiler isn't defined, should the build
process even be trying to copy those help files into (presumably)
rel2?
--
"Nature must be explained in
her own terms through
the experience of our senses."
Hans-Bernhard Bröker
2013-06-21 22:37:10 UTC
Permalink
Raw Message
Post by Paul S. Person
if the appropriate help compiler isn't defined, should the build
process even be trying to copy those help files into (presumably)
rel2?
I think it should. After all, somebody might have built help files and
stored the results in the right places (or network-mounted, say an
active OS/2 workspace's docs\os2 subdirectory there). If they're there,
it probably won't hurt to use them.

Loading...