I am working on packaging up the VM for Debian and related distros. My
current approach is to download the stable tarball release from
https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest. The
problem I'm having is that unless manual hacks are applied each time it is
downloaded, the build will fail since platforms/Cross/vm/sqSCCSVersion.h
has not been updated and the script to update it fails as the tarball is
just a snapshot of the source files rather than a clone of the repo. (the
snapshot is actually what is preferred vs a repo clone from a Debian
packaging standpoint)
Ideally, the generated tarball would include a pre-updated sqSCCSVersion.h
since this is a point in time snapshot. Is this something that makes sense
and could be changed for the generated tarball? If not, any suggestions on
how to handle this in an automated way for tarball builds? If I should be
sourcing the tarball a different way, I'm open to that as well.
Thanks,
Phil
Branch: refs/heads/Cog
Home: https://github.com/OpenSmalltalk/opensmalltalk-vm
Commit: ddc6ff03c69c051e1eeaf778b68997fb1c74bb1c
https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/ddc6ff03c69c051e1e…
Author: Eliot Miranda <eliot.miranda(a)gmail.com>
Date: 2021-07-16 (Fri, 16 Jul 2021)
Changed paths:
M build.macos32x86/common/Makefile.app
M build.macos64ARMv8/common/Makefile.app
M build.macos64x64/common/Makefile.app
M src/plugins/RePlugin/RePlugin.c
Log Message:
-----------
CogVM source as per VMMaker.oscog-eem.2987
Get rid of a compilation warning on 64 bits in the RePlugin.
In the Mac builds don't be confused by .dSYM hierarchies when fixing up @rpath
in dylibs.