I previously wrote:
> > 6. As a first step, I am merging in the v15.6
> > changes to my local v15.53e (Mac) software. When
> > I complete this task, I'll post the tarball
> > I'm also a bit confused by the assembly file
> > organization. The UNIX/Linux and PC variants have
> > a handful of ASM files, but the OS X (PowerPC)
> > port has a good score or two of assembly files.
>
> I think the people doing the port had not fully
> understood how poplog worked and may not have used
> the standard poplog mechanisms.
>
> However, I got the impression that many of the
> assembler files were simply left over from running
> pgcomp as part of the porting process.
I think you are right. Backed up all the *.a files
and then deleted all but the five assembly files
present in the Intel build, then rebuilt the newpop11
binary from the output of the pgcomp *.[ps]. This
produced a working executable, so I think they are
mostly unnecessary.
> > 1. The Pop11 sources should be merged into common
> > files that use preprocessor guards to separate
> > platform-specific code. (E.g., #_IF DEF WIN32 and
> > so forth).
This is done, except for some typo I introduced that
prevents lseek from working properly. I found that
there were a lot of "debug-style" wrappers around
some native OS calls (such as lseek). In removing
the wrappers, I think I broke something. But this
should be easy to fix.
> > 2. The platform-specific assembly files should
> > probably live in subdirectories of pop/src,
> > perhaps called pop/src/ppc and pop/src/x86. The
> > build tools should look in the appropriate
> > directory for the platform being built.
I ended up using subdirectories in src/powerpc,
src/x86, src/syscomp/powerpc, and src/syscomp/x86. I
think created symlinks from the appropriate files
to the root directory. This could be automated with
a script.
I have not attempted to build the ved or X11 part of
the sources, and will address those once the core
pop stuff builds properly.
In the meantime, does anyone have access to Subversion
or CVS hosting that could house the sources? I
don't want to muddy the waters on the OpenPoplog
sourceforge site since there are some differences
in focus and features in that version.
Thanks,
-Brent
|