Date: Wed, 17 Jun 2020 18:59:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 247352] devel/emscripten Introduce emscripten-devel port for bundled llvm and binaryen Message-ID: <bug-247352-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247352 Bug ID: 247352 Summary: devel/emscripten Introduce emscripten-devel port for bundled llvm and binaryen Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: yuri@freebsd.org Reporter: kpedersen@gmx.com Assignee: yuri@freebsd.org Flags: maintainer-feedback?(yuri@freebsd.org) Created attachment 215667 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D215667&action= =3Dedit An initial port diff for emscripten-devel Hello, Please find attached a port Makefile for emscripten-devel. This is very similar to the original emscripten port (written by yuri@freebsd.org) but it builds and bundles in the latest llvm (with just Host;WebAssembly targets). I feel this would be useful because emscripten is very dependent on the lat= est upstream llvm and if we can separate this from our version which may need to lag behind due to architecture related reasons this port will remain unaffected. You can see in the port it uses the very latest versions from github (as revision hashes). I recently had my minor change pulled into the emscripten repo recently so it might be one or two revisions out by now. This port also handles the generation of ~/.emscripten a little differently. Normally the first time the compiler is run it generates this file and exit= s, causing issues with our build server. This generates the file and then carr= ies on with the compilation. This port also avoids hard coding paths in the .emscripten file making it easier to use multiple versions. I added a CONFLICTS to the current emscrip= ten but with a few tweaks we could make both run side by side. Finally my future goal is to create an emscripten-ports-devel port which bundles up the few (9?) ports for various emscripten libraries and adds the= m to ${EMSCRIPTEN_PREFIX}/system/local. The current solution downloads them as needed which I find a little bit too "web dev" for my liking. I prefer deterministic builds. This initial work can be seen here: https://github.com/osen/emscripten-devel Many thanks, Karsten kpedersen@gmx.com --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247352-7788>