Bug#1013214: O: asmjit -- Complete x86/x64 JIT and AOT Assembler for C++

To: 1013214@bugs.debian.org
Subject: Bug#1013214: O: asmjit -- Complete x86/x64 JIT and AOT Assembler for C++
From: Andrius Merkys <merkys@debian.org>
Date: Tue, 25 Oct 2022 09:03:52 +0300
Message-id: <[🔎] 9d915e7e-383c-8393-a74a-08cfd658a14d@debian.org>
Reply-to: Andrius Merkys <merkys@debian.org>, 1013214@bugs.debian.org
In-reply-to: <17647062d086cc49eeb5d8d12edc62736efc9b0e.camel@riseup.net>
References: <17647062d086cc49eeb5d8d12edc62736efc9b0e.camel@riseup.net> <17647062d086cc49eeb5d8d12edc62736efc9b0e.camel@riseup.net> <17647062d086cc49eeb5d8d12edc62736efc9b0e.camel@riseup.net>

Hello,

I have stumbled upon asmjit while packaging openmm. Asmjit is alsoembedded at least in erlang and mame [1], thus packaging it might be agood idea. However, asmjit is not yet stable [2], thus the sharedlibrary approach might not be appropriate: breaking changes willinterfere with shared library handling in Debian and are likely to causemess if sonames are not changed. A bit better approach, IMO, would be toship static library. Anyway it is quite early to unembed asmjit fromother sources.

[1]https://codesearch.debian.net/search?q=This+file+is+part+of+AsmJit+project&literal=1

[2] https://asmjit.com/doc/group__asmjit__breaking__changes.html

Andrius

Reply to:

Prev by Date: Processed: Changing forks
Next by Date: Bug#543821: marked as done (O: fusesmb -- filesystem client based on the SMB file transfer protocol)
Previous by thread: Processed: Changing forks
Next by thread: Bug#543821: marked as done (O: fusesmb -- filesystem client based on the SMB file transfer protocol)
Index(es):
- Date
- Thread