Hi,
what should the string for MARCH be in the deken file name for Intel compatible processors, the deken documentation is unclear here:
- 64 bit: amd64 or x86_64? AFAIK both mean the same thing, but are used in different contexts, most Linux distros use amd64, while on Windows x64 (Visual Studio) and x86_64 (MinGW) are used, no idea about Mac.
- 32 bit: i386 or x86? Linux distros use i386, Windows x86, no idea about Mac.
The examples use both 64 bit versions, inconsistent in the usage: https://github.com/pure-data/deken/blob/master/developer/README.md#filename-...
Thanks, Thomas
On 04/28/2018 02:04 AM, Thomas Mayer wrote:
Hi,
what should the string for MARCH be in the deken file name for Intel compatible processors, the deken documentation is unclear here:
- 64 bit: amd64 or x86_64?
AFAIK both mean the same thing, but are used in different contexts, most Linux distros use amd64, while on Windows x64 (Visual Studio) and x86_64 (MinGW) are used, no idea about Mac.
use "amd64" (although "x86_64" is allowed as well, the former is more concise and used by the 'deken' cmdline utility)
- 32 bit: i386 or x86?
Linux distros use i386, Windows x86, no idea about Mac.
"i386".
ideally, you should just (be able to) use the "deken" cmdline utility, which will figure out the architectures by itself. (it can also generate an objectlist, a gpg signatures and a sha256 hash file; and upload everything)
gfmdsar IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi,
On 28.04.2018 23:13, IOhannes m zmölnig wrote:
ideally, you should just (be able to) use the "deken" cmdline utility, which will figure out the architectures by itself. (it can also generate an objectlist, a gpg signatures and a sha256 hash file; and upload everything)
ideally, yes. But I do not have real machines will all architectures available, so I am cross-compiling and packaging with Travis, and then upload the .dek files to my server, where I can get them and the upload them via the command line utility. Is there a way to call deken to override the architecture, version and float size via options?
Thanks, Thomas - -- "When one's home has a really excellent computer capable of reaching other computers anywhere in the Galaxy, one scarcely needs to budge." (Janov Pelorat in: Isaac Asimov - Foundation's Edge) http://www.residuum.org/
On 04/30/2018 12:03 AM, Thomas Mayer wrote:
Hi,
On 28.04.2018 23:13, IOhannes m zmölnig wrote:
ideally, you should just (be able to) use the "deken" cmdline utility, which will figure out the architectures by itself. (it can also generate an objectlist, a gpg signatures and a sha256 hash file; and upload everything)
ideally, yes. But I do not have real machines will all architectures available, so I am cross-compiling and packaging with Travis, and then upload the .dek files to my server, where I can get them and the upload them via the command line utility. Is there a way to call deken to override the architecture, version and float size via options?
the deken cmdline utility will take the actual architectures of the binaries it finds, not some wild guesses based on the current architecture.
gfdas IOhannes
-
IOhannes m zmölnig -
Thomas Mayer