Replies: 29 comments 81 replies
|
Can you tell me where I can help? (here or at the FreeBSD forum) |
|
Hi Patrick, This is the thread I opened on the FreeBSD forum: https://forums.freebsd.org/threads/first-time-trying-to-create-a-port-i-need-guidance.101145/ However, I am at the very initial stage and I don't need your help yet, I am still wrapping my head around the ports. |
|
I mean: which part of the build process or something else can I help? |
|
Got you. I was able to build locally Publisher, creating a port is something else, I will definitely ask for your help as soon as I am going to need it. I am still trying to figuring out the basic stuff, and I am very slow to grasp this stuff... 😓 |
|
Hi Patrick, From the forum they are suggesting to create a port for the Is that assumption correct for you? |
|
When you say "sheel script" you mean that is possible to build |
|
Yes. See the buildlib and buildsp files https://github.com/speedata/publisher/tree/develop/src/go/sphelper. They just call cc or go build to compile the stuff and finally (distcustom) moves files to the right position. No magic involved |
|
Thank you Patrick, I hope to start doing something better this week... 🙏 |
|
I asked to the LLM to extract and condensed into a bash script the instructions inside the files you recommended... I am going to verify and to test them... Although I feel pretty ashamed for having done that... 😟 |
|
Don't tell anybody: I do that all the time.... |
|
Hi Patrick, I am circling around without getting anything. Is this the code to create the sp binary? |
|
No, this is the source code of the sp binary. To create the binary, sphelper is used: src/go/sphelper/buildsp/buildsp.go |
|
Got you! I fell into the AI rabbit hole, and it is very dramatic when you know lesser than the LLM model... 😩 |
|
Hi Patrick, this has been a little bit frustrating, "vibe coding", hasn't been a pleasant activity. I believe these scripts work fine now, the main one creates the libraries and the binary, plus some instructions for the distribution on where copies the files created; the second one is to clean up with mess. It couldn't be possible to create a single script cause even DeepSeek doesn't have enough memory to store all that characters. If you don't mind to check these scripts it would be really beneficial, so I can start moving on the FreeBSD part! 🙏 |
|
Scripts are too long to be pasted. |
|
I do believe that I need to find a better tool. I ended up with DeepSeek cause it can handle more characters, but the blanket is too small, when it fixes something it introduces a regression somewhere else. Then I realized that it was patching sp.go during the building time. |
|
This is what Claude tells me: Thanks for working on FreeBSD support! I had a look at the script and compared it against the internal build system (src/go/sphelper/buildlib/buildlib.go and buildsp/buildsp.go). Here are a few Build mode: dest=custom for FreeBSD ports Since this is for a FreeBSD port installing to /usr/local, the right build mode is dest=custom. This lets you compile the library and resource paths directly into the binary. The existing dest modes
For FreeBSD, the build command should be: go build -ldflags "-X main.dest=custom The variables main.version, main.dest, main.libdir, and main.srcdir are already declared in src/go/sp/sp/sp.go (lines 56-60) and are designed to be set this way. The script currently creates a luaglue source location The script searches for C files in src/go/splib/, but the luaglue source lives at src/c/luaglue.c. The correct build command (matching buildlib.go line 54) is: cc -shared -fPIC -o luaglue.so luaglue.c -I/usr/local/include/lua53/ CGO flags The script sets CGO_LDFLAGS="-L/usr/local/lib -llua-5.3", but the upstream build doesn't set CGO_LDFLAGS for FreeBSD (or Linux). The Lua binding works through luaglue.so rather than direct linking, Go package path Instead of searching for func main() with find/grep (which could also match sphelper's main), the package path is simply speedatapublisher/sp/sp — that's what the build system uses. Resource installation Beyond the binaries, the Publisher needs its resource files at runtime. For a dest=custom build, main.srcdir points to where these are expected. The install step should copy:
And the shared libraries go to lib/speedata-publisher/:
Note that sdluatex (the LuaTeX engine) is also required — sp looks for it first in installdir/bin/, then in PATH (see sp.go lines 506-531). Smaller things
I put together a revised version of the script based on these findings that uses dest=custom, proper ldflags, DESTDIR/PREFIX support, and an install target: |
|
Thank you Patrick, I spent more than one week with generic tools without getting anything on the end. I am going to start again from your hint. However these day I noticed that I am not very good at writing prompts. As designer I spent many years to improve my critical-thinking, in terms of "non-linear" thinking, and I believe these models are design, or work better, toward linear-thinking. What prompt did you use to get your code done? |
|
I can't remember. I use claude code and wrote something like this "here is a script to create a package of the speedata Publisher on freebsd. Do you have any helpful suggestions?" and pasted the script. |
|
Thank you Patrick, I'll start again I hope to get something by the end of this week... 🙏 |
|
Hi Patrick, Claude looks better. Is this correct? |
|
I see that the saxon libs are missing |
|
Thank you, good catch... Let me speak with Claude... |
|
Hi Patrick, I updated the tree above, is it now correct? |
|
Looks good to me. |
|
Great, thank you Patrick! 🙏 |
|
Hi Patrick, Good news, it looks like I have a fully shell script that works: #!/bin/sh
#
# sphelper.sh - FreeBSD build and installation helper for speedata Publisher
# POSIX-compliant shell script
#
# Exit on error
set -e
# Default configuration
: ${BASEDIR:=$(pwd)}
: ${BUILDDIR:=${BASEDIR}/build}
: ${SRCDIR:=${BASEDIR}/src}
: ${PREFIX:=/usr/local}
: ${BINDIR:=${PREFIX}/bin}
: ${SHAREDIR:=${PREFIX}/share/speedata-publisher}
: ${LIBDIR:=${SHAREDIR}/lib}
: ${SWDIR:=${SHAREDIR}/sw}
: ${SCHEMADIR:=${SHAREDIR}/schema}
: ${DYLIBBUILD:=${BUILDDIR}/dylib}
# Detect version from version file if not set
if [ -z "${VERSION}" ]; then
if [ -f "${BASEDIR}/version" ]; then
VERSION=$(grep '^publisher_version=' "${BASEDIR}/version" | cut -d'=' -f2 | tr -d '[:space:]')
else
VERSION="unknown"
fi
# If still empty, set to unknown
if [ -z "${VERSION}" ]; then
VERSION="unknown"
fi
fi
: ${SDPRO:="no"}
# FreeBSD specific settings
GOOS="freebsd"
GOARCH=$(uname -m)
case "${GOARCH}" in
amd64|x86_64)
GOARCH="amd64"
;;
i386|i686)
GOARCH="386"
;;
aarch64|arm64)
GOARCH="arm64"
;;
armv7*)
GOARCH="arm"
;;
*)
echo "Unsupported architecture: ${GOARCH}"
exit 1
;;
esac
# Lua include path for FreeBSD
LUA_INCLUDE="/usr/local/include/lua53"
# Display usage information
usage() {
cat << EOF
Usage: $(basename "$0") <command> [options]
Commands:
build Build sp binary for FreeBSD
buildlib Build sp libraries for FreeBSD
install Install speedata Publisher to ${PREFIX}
uninstall Uninstall speedata Publisher from ${PREFIX}
clean Clean all build artifacts and downloads
Environment Variables:
BASEDIR Base directory (default: current directory)
BUILDDIR Build output directory (default: \$BASEDIR/build)
SRCDIR Source directory (default: \$BASEDIR/src)
PREFIX Installation prefix (default: /usr/local)
SDPRO Build Pro version (yes/no, default: no)
VERSION Publisher version (auto-detected from version file)
Examples:
$(basename "$0") buildlib
$(basename "$0") build
SDPRO=yes $(basename "$0") build
sudo $(basename "$0") install
sudo $(basename "$0") uninstall
$(basename "$0") clean
EOF
}
# Create sdluatex symbolic link
create_sdluatex_link() {
if [ ! -e "${BINDIR}/sdluatex" ]; then
echo "Creating symbolic link: ${BINDIR}/sdluatex -> ${BINDIR}/luahbtex"
ln -sf "${BINDIR}/luahbtex" "${BINDIR}/sdluatex"
fi
}
# Build the main sp binary
build_sp() {
local destdir="$1"
local target_os="${2:-${GOOS}}"
local target_arch="${3:-${GOARCH}}"
echo "Building sp binary for ${target_os}/${target_arch}"
# Ensure destination directory exists
mkdir -p "${destdir}"
# Verify source directory exists and find the correct build path
sp_source_dir=""
if [ -d "${SRCDIR}/go/sp/sp" ] && [ -n "$(find "${SRCDIR}/go/sp/sp" -maxdepth 1 -name "*.go" -type f 2>/dev/null)" ]; then
sp_source_dir="${SRCDIR}/go/sp/sp"
elif [ -f "${SRCDIR}/go/sp/main.go" ]; then
sp_source_dir="${SRCDIR}/go/sp"
else
echo "Error: Cannot find sp source directory with .go files"
echo "Tried:"
echo " ${SRCDIR}/go/sp/sp/"
echo " ${SRCDIR}/go/sp/main.go"
exit 1
fi
echo " Source: ${sp_source_dir}"
# Set Go build environment
export GOOS="${target_os}"
export GOARCH="${target_arch}"
export CGO_ENABLED=1
# Build flags - inject paths and version for custom mode
ldflags="-X main.dest=custom"
ldflags="${ldflags} -X main.version=${VERSION}"
ldflags="${ldflags} -X main.libdir=${LIBDIR}"
ldflags="${ldflags} -X main.srcdir=${SWDIR}"
# Add Pro flag if enabled
if [ "${SDPRO}" = "yes" ]; then
ldflags="${ldflags} -X main.pro=yes"
fi
# Strip symbols for smaller binary
ldflags="${ldflags} -s"
# Debug output
echo "Build environment:"
echo " BASEDIR=${BASEDIR}"
echo " GOOS=${GOOS}"
echo " GOARCH=${GOARCH}"
echo " CGO_ENABLED=${CGO_ENABLED}"
echo " Version=${VERSION}"
echo " Pro=${SDPRO}"
echo " libdir=${LIBDIR}"
echo " srcdir=${SWDIR}"
echo " Output: ${destdir}/sp"
# Navigate to source directory
cd "${sp_source_dir}" || {
echo "Error: Cannot cd to sp source directory: ${sp_source_dir}"
exit 1
}
# Build the sp binary
echo "Running: go build -ldflags \"${ldflags}\" -o \"${destdir}/sp\""
go build -ldflags "${ldflags}" -o "${destdir}/sp"
build_result=$?
if [ ${build_result} -eq 0 ]; then
chmod +x "${destdir}/sp"
echo "Successfully built sp binary: ${destdir}/sp"
# Verify the binary
if [ ! -f "${destdir}/sp" ]; then
echo "Error: Binary file was not created"
exit 1
fi
# Check if it's a valid ELF binary
file "${destdir}/sp" | grep -q "ELF"
if [ $? -ne 0 ]; then
echo "Warning: Output file may not be a valid ELF binary"
file "${destdir}/sp"
fi
echo ""
echo "Build complete!"
else
echo "Error: Failed to build sp binary (exit code: ${build_result})"
exit 1
fi
}
# Build the Go dynamic library (libsplib.so)
build_go_lib() {
local target_os="$1"
local target_arch="$2"
echo "Building dynamic library for ${target_os} ${target_arch}"
# Ensure dylib build directory exists
mkdir -p "${DYLIBBUILD}"
# Set environment for CGO
export GOOS="${target_os}"
export GOARCH="${target_arch}"
export CGO_ENABLED=1
export CGO_CFLAGS="-I${LUA_INCLUDE}"
# Navigate to splib source
cd "${SRCDIR}/go/splib" || {
echo "Error: Cannot find splib source directory"
exit 1
}
# Build the shared library
go build -buildmode=c-shared -o "${DYLIBBUILD}/libsplib.so" .
if [ $? -eq 0 ]; then
echo "Successfully built libsplib.so"
else
echo "Error: Failed to build libsplib.so"
exit 1
fi
}
# Build the C glue library (luaglue.so)
build_c_lib() {
local target_os="$1"
local target_arch="$2"
echo "Building dynamic lua glue library for ${target_os} ${target_arch}"
# Ensure dylib build directory exists
mkdir -p "${DYLIBBUILD}"
# Navigate to C source directory
cd "${SRCDIR}/c" || {
echo "Error: Cannot find C source directory"
exit 1
}
# Compile the C glue library
case "${target_os}" in
freebsd)
cc -shared -fPIC -o "${DYLIBBUILD}/luaglue.so" \
luaglue.c -I"${LUA_INCLUDE}"
;;
*)
echo "Error: Unsupported OS for C library: ${target_os}"
exit 1
;;
esac
if [ $? -eq 0 ]; then
echo "Successfully built luaglue.so"
else
echo "Error: Failed to build luaglue.so"
exit 1
fi
}
# Build both libraries
build_libraries() {
local target_os="${1:-${GOOS}}"
local target_arch="${2:-${GOARCH}}"
build_go_lib "${target_os}" "${target_arch}"
build_c_lib "${target_os}" "${target_arch}"
echo "Libraries built successfully in ${DYLIBBUILD}"
echo ""
echo "Next step: Build the sp binary with:"
echo " ./sphelper.sh build"
}
# Install speedata Publisher
install_publisher() {
echo "Installing speedata Publisher to ${PREFIX}"
echo ""
# Check if we have the necessary files
if [ ! -f "${BASEDIR}/bin/sp" ]; then
echo "Error: sp binary not found. Run './sphelper.sh build' first."
exit 1
fi
if [ ! -f "${DYLIBBUILD}/libsplib.so" ] || [ ! -f "${DYLIBBUILD}/luaglue.so" ]; then
echo "Error: Libraries not found. Run './sphelper.sh buildlib' first."
exit 1
fi
# Create directory structure
echo "Creating directory structure..."
mkdir -p "${BINDIR}"
mkdir -p "${LIBDIR}/lib"
mkdir -p "${SCHEMADIR}"
mkdir -p "${SWDIR}/colorprofiles"
mkdir -p "${SWDIR}/fonts"
mkdir -p "${SWDIR}/hyphenation"
mkdir -p "${SWDIR}/img"
mkdir -p "${SWDIR}/lua"
mkdir -p "${SWDIR}/metapost"
mkdir -p "${SWDIR}/tex"
# Install binary
echo "Installing binary..."
install -m 755 "${BASEDIR}/bin/sp" "${BINDIR}/sp"
# Create sdluatex symlink
create_sdluatex_link
# Install libraries
echo "Installing libraries..."
install -m 644 "${DYLIBBUILD}/libsplib.so" "${LIBDIR}/libsplib.so"
install -m 644 "${DYLIBBUILD}/luaglue.so" "${LIBDIR}/luaglue.so"
# Install JAR files
echo "Installing JAR utilities..."
install -m 644 "${BASEDIR}/lib/jing.jar" "${LIBDIR}/jing.jar"
install -m 644 "${BASEDIR}/lib/saxon-he-12.9.jar" "${LIBDIR}/saxon-he-12.9.jar"
install -m 644 "${BASEDIR}/lib/trang.jar" "${LIBDIR}/trang.jar"
install -m 644 "${BASEDIR}/lib/lib/xmlresolver-5.3.3-data.jar" "${LIBDIR}/lib/xmlresolver-5.3.3-data.jar"
install -m 644 "${BASEDIR}/lib/lib/xmlresolver-5.3.3.jar" "${LIBDIR}/lib/xmlresolver-5.3.3.jar"
# Install schema files
echo "Installing schema files..."
install -m 644 "${BASEDIR}/schema/catalog-schema-de.xml" "${SCHEMADIR}/"
install -m 644 "${BASEDIR}/schema/catalog-schema-en.xml" "${SCHEMADIR}/"
install -m 644 "${BASEDIR}/schema/layoutschema-de.rng" "${SCHEMADIR}/"
install -m 644 "${BASEDIR}/schema/layoutschema-de.xsd" "${SCHEMADIR}/"
install -m 644 "${BASEDIR}/schema/layoutschema-en.rng" "${SCHEMADIR}/"
install -m 644 "${BASEDIR}/schema/layoutschema-en.xsd" "${SCHEMADIR}/"
# Install sw files
echo "Installing source files to ${SWDIR}..."
# colorprofiles
cp -R "${SRCDIR}/colorprofiles/"* "${SWDIR}/colorprofiles/"
# fonts
cp -R "${BASEDIR}/fonts/"* "${SWDIR}/fonts/"
# hyphenation
cp -R "${SRCDIR}/hyphenation/"* "${SWDIR}/hyphenation/"
# img
cp -R "${BASEDIR}/img/"* "${SWDIR}/img/"
# lua (recursive)
cp -R "${SRCDIR}/lua/"* "${SWDIR}/lua/"
# metapost
cp -R "${SRCDIR}/metapost/"* "${SWDIR}/metapost/"
# tex
cp -R "${SRCDIR}/tex/"* "${SWDIR}/tex/"
echo ""
echo "Installation complete!"
echo ""
echo "speedata Publisher ${VERSION} installed to ${PREFIX}"
echo ""
echo "To verify installation:"
echo " sp --version"
echo ""
}
# Uninstall speedata Publisher
uninstall_publisher() {
echo "Uninstalling speedata Publisher from ${PREFIX}"
echo ""
# Remove binary
echo "Removing binary..."
rm -f "${BINDIR}/sp"
rm -f "${BINDIR}/sdluatex"
# Remove entire speedata-publisher directory
echo "Removing installation directory..."
rm -rf "${SHAREDIR}"
echo ""
echo "Uninstallation complete!"
echo "speedata Publisher has been removed from ${PREFIX}"
echo ""
}
# Clean build artifacts
clean_build() {
echo "Cleaning build artifacts..."
echo ""
# Remove build directory
if [ -d "${BUILDDIR}" ]; then
echo "Removing ${BUILDDIR}"
rm -rf "${BUILDDIR}"
fi
# Remove built binaries
if [ -f "${BASEDIR}/bin/sp" ]; then
echo "Removing ${BASEDIR}/bin/sp"
rm -f "${BASEDIR}/bin/sp"
fi
# Remove Go build cache and downloaded modules
echo "Cleaning Go cache..."
go clean -cache -modcache 2>/dev/null || true
echo ""
echo "Clean complete!"
echo "All build artifacts have been removed."
echo ""
}
# Main command dispatcher
main() {
if [ $# -eq 0 ]; then
usage
exit 1
fi
command="$1"
shift
case "${command}" in
build)
# Build the sp binary
build_sp "${BASEDIR}/bin"
;;
buildlib)
# Build libraries for current architecture
build_libraries
;;
install)
# Install speedata Publisher
install_publisher
;;
uninstall)
# Uninstall speedata Publisher
uninstall_publisher
;;
clean)
# Clean build artifacts
clean_build
;;
help|--help|-h)
usage
exit 0
;;
*)
echo "Error: Unknown command '${command}'"
echo ""
usage
exit 1
;;
esac
}
# Run main function
main "$@" |
|
Now my request is if you can recommend me some test to run to see if everything is working fine! Thanks in advance... 🙏 |
|
https://doc.speedata.de/publisher/en/helloworld/
creates a directory named 'helloworld' with two files, go to the directory and run "sp". That's it. You can also clone https://github.com/speedata/examples/ and try the examples there. |
|
Cool, the first basic test worked out. I'll run all the examples; and what about filters and the other tools? 🙏 |
|
Try the https://github.com/speedata/examples/tree/master/shakespeare example: run Other tools (really system depending) for example the charts (read svg files with inkscape) |
|
After installed Inskscape, The other command looks it worked as well: |
|
I got some errors in some files:
|
I'll fix it or remove it. Very old example..... Thank you for the hint |
|
It works with |
|
Yes it worked. |
|
The news example doesn't work with the new xpath parser due to a bug in sp. I'll fix this tomorrow. |
|
... fixed in 5.3.23 |
|
Good news, I created a local port that builds Publisher. |
|
This is probably a freebsd question, I don't know their policy. |
|
I can figure out this later. I have question, I am taking the source from the Github "tags" , but where can I let the ports download the "stable" from? 🤷♂️ |
|
The stable are also tagged, the have an even number in the middle (where 0 is also even). So 5.0.x is stable, 5.1.x is unstable, 5.2.x stable and so on. Does this help? |
|
Hi Patrick, I am hating myself for relying on Claude; but it says that it will be ok... |
|
What is "tab release"? |
Anyway, it seems totally unnecessary. |
|
That one! I understand, but I deliberately don't put releases there (not to have too many different places for binaries). |
|
I see. |
|
no worries, we will get it to work together! |
|
Congrats for 5.4... 🍾🍾🍾 This is very good also to test my ports out. |
|
Good news Patrick! I was finally able to build I am going to perform some tests, and hopefully I can submit the port on Monday... 🙏 |
|
Hi Patrick, I have publisher stable and publisher devel ready for review. I need to re-run them into the examples directory. Thanks... 🙏 |
|
There is the qa directory for that. Most of the time when I hit an error, I try to create a layout in the qa directory for it and compare it to the reference pdf. I don't have a tricky layout (not even one that is not publicly available). Of course, every layout needs different features, but I would not consider them tricky or nasty ;-) |
|
Got you. Won't repeat this request twice! 😓 |
|
Hi Patrick, so far this is the only document where I fail. jsonreader ) sp --version
Version: 5.4.0 (Pro)
jsonreader ) sp --loglevel debug --verbose
Config files read: /home/freezr/git/examples/technical/jsonreader/publisher.cfg
[-jar /usr/local/share/speedata-publisher/lib/saxon-he-12.9.jar -xsl:json2xml.xsl -o:data.xml -it:main filename=us-500.json]
Exception in thread "main" java.lang.NoClassDefFoundError: org/xmlresolver/Resolver
at net.sf.saxon.lib.CatalogResourceResolver.<init>(CatalogResourceResolver.java:46)
at net.sf.saxon.Configuration.init(Configuration.java:387)
at net.sf.saxon.Configuration.<init>(Configuration.java:234)
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
at java.base/java.lang.reflect.ReflectAccess.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.ReflectionFactory.newInstance(Unknown Source)
at java.base/java.lang.Class.newInstance(Unknown Source)
at net.sf.saxon.Configuration.newConfiguration(Configuration.java:250)
at net.sf.saxon.s9api.Processor.<init>(Processor.java:83)
at net.sf.saxon.Transform.doTransform(Transform.java:327)
at net.sf.saxon.Transform.main(Transform.java:85)
Caused by: java.lang.ClassNotFoundException: org.xmlresolver.Resolver
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
... 12 more
exit status 1
java -jar /usr/local/share/speedata-publisher/lib/saxon-he-12.9.jar -xsl:json2xml.xsl -o:data.xml -it:main filename=us-500.jsonand... Perhaps I need a different version of Java, by default it is installed: |
|
Can you show the output of |
|
For some reason I created an additional dir |
|
Claude spotted and |
|
Hi Patrick, please take this with a grain of salt:
58-}
59-
60-func runSaxon(l *lua.LState) int {
61- numberArguments := l.GetTop()
62- var command []string
63: command = []string{"-jar", filepath.Join(libdir, "saxon-he-12.9.jar")}
64- if numberArguments == 1 {
65- // hopefully a table
66- lv := l.Get(-1)
67- if tbl, ok := lv.(*lua.LTable); ok {
68- m := map[string]string{
69- "initialtemplate": "-it:%s",
70- "source": "-s:%s",
71- "stylesheet": "-xsl:%s",
72- "out": "-o:%s",
73- }
the key information is:
|
|
Thank you very much, I'll include this in the next version of the publisher (stable and development) |
|
I finally submitted the request for both stable and devel version... 🤞 |
|
Hi Patrick, The jar files cannot be included (this is what I understood) as is; the recommendation is to use the ones available on FreeBSD, and if a specific version is required it might be applied an exception, but these jar file must be built from source and therefore java must be another dependency. For what I've understood so far, these java tools aren't a requirement to build Publisher, and might be downloaded separately, I wonder if is not too much trouble for you to release also a tarball that doesn't contain bundled jar files. But if I got this wrong and these jar tools are necessary to perform specific functions than I guess to begin I could start by using the ones available on the system for the sake of building the port. Here the discussion: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293790 Thanks... 🙏 |
if there is another option, I'd rather not create a separate zip bundle without the jar files. I am not sure what the current way to create a port is. Would it be possible to just remove the jar files after downloading the ZIP file? |
|
Hi Patrick, I totally understand, I was exploring potentially solutions. Thanks... 🙏 |
|
They are just a runtime requirement and only for the case the user wants to run saxon to transform XML with XSLT. I will add a configuration to specify a different path for saxon, so this can be easily solved. |
|
Cool! 🙏 |
|
Hi Patrick, I am moving forward with the port. A problem that I couldn't find a good solution is about the third parties java (jar) app. The Ports team is asking to get them from the ports. I am doing this task with Claude so it needs to verify the following:
If neither is straightforward, I ( Thanks in advance… 🙏 |
|
1: 12.8 will be fine |
|
Thank you very much! 🙏 |
|
The current version (5.5.24) has options to configure the location of the jar files: See the installation section Saxon is now version independent and falls back to 12.9 if nothing else is found. |
|
This sounds great! I am still dealing with porting stable, eventually I will have the port accepted and I can move on the development port. The idea of Publisher working on ZFS is very thrilling, I can't wait to be able to install it as regular port... 🙏 |
|
Hi Patrick, I am checking into AArch64, with the current
What's your workaround for AArch64 on Apple about this |
|
macOS works fine, but I think FreeBSD/arm might be a show-stopper :-( I don't know much about this topic, so I asked Caude: Good question. Short version: on Apple Silicon there is no workaround — Go supports So the question really is: what to do about Why this is an allowlist problem, not a toolchain problem
Producing a shared object from Go cgo code needs three things, all of which FreeBSD/arm64 already has:
The patch, if you want to try itTwo files in a local Go source build:
case "c-shared":
switch platform {
case "linux/amd64", "linux/arm", "linux/arm64", …,
- "freebsd/amd64",
+ "freebsd/amd64", "freebsd/arm64",
"darwin/amd64", "darwin/arm64",
…:
return true
}
Then Validation, smallest step firstBefore touching the publisher build, sanity-check Go itself: cd src/go/splib
GOOS=freebsd GOARCH=arm64 CGO_ENABLED=1 \
/path/to/patched/go build -buildmode=c-shared \
-o /tmp/libsplib.so speedatapublisher/splibIf that produces a Caveats
|
|
Thank you Patrick, Patching GO is out of discussion, asking you to refactor something either. For the moment FreeBSD won't have an ARM build if my port is going to be accepted. We will try to put some pressure on the GO project to allow building for ARM on FreeBSD as well. Thank you very much! 🙏 |
|
Hi Patrick, With 5.6 released the Ports Team told me that is fine if I sent patch for 5.6 rather than 5.4.3. What confused me (and Claude) is about lua-5.4 (lua54 on FreeBSD), I need some clarification about the different version of Lua-5.3 and tex-luatex (based on Lua 5.3) we'll be continued to be used to build the Publisher binary. Is that correct? Any additional information is welcomed! Thanks in advance! 🙏 |
|
Short answer: yes, correct. Longer answer: There are two Lua versions involved:
So when it comes to packaging the speedata Publisher, I think none of this should be noteworthy, since 5.3 is included in the LuaTeX binary (called sdluatex in my distribution), and 5.4 is only of concern when you use the I hope this answers the question. |
|
Thank you Patrick, it is OK! 👍 Unfortunately, I have to take a stop for a month, I will start again on July. I hope to get the port accepted before August... 🙏 |
|
Hi Patrick, great news!!! https://www.freshports.org/print/publisher/ Robert Clausecker, the guy, that was helping me in this process, made the extra-mile and fixed the last detail to make this port through so next stable will be easier to port as simple update patch! He was incredible, he lead me all way down through the process, without his help this wouldn't be possible. For the next stable the challenge would be the following:
I wonder if also for If this would result in too much work for you, maybe you can lead the path, and I will try to get there with the aid of Claude. In the meantime happy Publisher on FreeBSD!!! 🍾🍾🍾 |
|
Congratulations! Question: would it be possible or feasible to create a file I will extend the sp program to look for a luahbtex binary. |
|
Version 5.7.0 now looks for luahbtex if sdluatex is not found (untested though) |
|
This is great! 💪 I'd like to ask you, what source file should I let Claude analyze to try to patch the current stable (5.6) in order to use Thanks! 🙏 |
|
Point claude to 12c07a1d It is sp.go line 517 and following. |
|
Good news I let Claude back-port this patch on 5.6.0 and it worked out. I tested:
And it was all good! 👍 I wonder if for the next version when you run Unless you don't think that is totally irrelevant. Thanks... 🙏 |
|
Next version will have an extended |
|
Yes, totally! 👍 |
|
5.7.5 with |
|
Hi Patrick, I want to confirm that your new feature works fine on FreeBSD: 🙏 |
|
Hi Patrick, I was on vacation and now I am trying to catch up to push 5.6.0 and starting the process for the development version. I have a couple of questions (if you are available of course):
Thanks in advance! 🙏 |
|
I assume you need Lua 5.3 headers. LuaTeX and the speedata Publisher both are self contained, for compiling the latter you need the headers. (I might be wrong though, not really a compile-savvy person) Lua 5.4 is definitely incorrect, but I have no idea if they work (I guess not) |
|
I believe I pretty confused, I am sorry. You wrote:
Is this go version be build during the compilation time? Or do I need to add it as dependency in the makefile? |
|
The Go version is compiled during compilation time, but this is a pure Go implementation, so no C-header files are necessary. It is included in the sp binary. |
|
Thanks! 🙏 I guess I am fine, I need only to test it on Poudriere then. |
|
Hi Patrick, I submitted the request for 5.6 and back ported the patch from 5.7.2 so now also the stable looks for Now the new guy assigned to review my submission told me that on his end it builds also with Lua 5.4 and he was asking me why not 5.4 instead of 5.3. I copied a comment you made, and I told him that this may lead some instabilities or missing functionalities, but I only guessed. What is your take on Lua 5.4? Thanks… 🙏 |
|
This is beyond my knowledge. It might work, but I don't know what will happen. Since this will only be used during compile time (not during run time), it will work if the header files are compatible. I am not much into compiling things, I am happy when an executable or a library comes out. |
|
Hi Patrick, It is fine to use Lua5.3 if it is required by the software. |
|
Lua 5.3 is hardcoded in the LuaTeX binary, no visible plan to update it to 5.4. (Out of my scope, and not user visible anyway) The filter is 5.4 but a Go interpreter and self contained, so this is all set. |
|
Got you, thanks for the explanation. I don't remember if I ever told you about this, but the FreeBSD Third-Party Ports allow for package flavors, in this case the PRO version is a flavor of the regular Publisher package. Flavors can be distributed as binary package or as source to compile. Publisher PRO flavor is not distributed as binary, it must be compiled from source. Thanks... 🙏 |
Uh oh!
There was an error while loading. Please reload this page.
Hi Patrick,
I've started the process to port Publisher on FreeBSD (my account on FreeBSD is still in probationary though):
https://forums.freebsd.org/threads/first-time-trying-to-create-a-port-i-need-guidance.101145/
This is the first time for me, so I am learning by doing. The documentation is very well done and the people on the forum willing to help me:
https://docs.freebsd.org/en/books/porters-handbook/porting-why/
I am opening this discussion for getting help on your side!
Thank you very much! 🙏
All reactions