PACK 64.7z ^NEW^
Packaged versions of Octave for GNU/Linux systems are provided by theindividual distributions described in theOctave wiki.These packages are created by volunteers.The delay between an Octave source release and the availability of a packagefor a particular GNU/Linux distribution varies.
PACK 64.7z
Executable versions of Octave for BSD systems are provided by the individualdistributions.Both FreeBSD and OpenBSDhave Octave packages.These packages are created by volunteers and the Octave project has no controlover that process.
I wanted to open an issue at GitHub - obsidianmd/obsidian-releases: Community plugins list, theme list, and releases of Obsidian. to ask for a flat ZIP which contains the content of app-64.7z but there is no option to open an issue.
Regarding the installer that ultimately gets made and will be run by a user, the installer will create a directory on the user computer that mirrors the "build/win-unpacked" directory that gets made by electron-builder. At least this is the behavior in my setup. I'll refer to that as the "unpacked" directory.
The section called extraFiles will let you define extra files/folders that you can copy into your unpacked directory, from the files that are available to the builder. So I wanted to just copy this one folder called eepromStaging from my project root directory, into the unpacked root directory. And I also wanted to copy & paste this folder of binary files from my project into the unpacked directory. And these files are "extra": they're files that get added to your unpacked directory on top of everything else. The "filter": ["**/*"] means that all of the files and folders are going to be copied over.
I tested out the above configuration and it works for me: I'm able to make an exe installer that installs all my extra binary files in the correct location. However... in my configuration, I have to use vue.config.js, and if I try to add these properties to my package.json, it doesn't work. Ultimately though, these properties that I'm defining in vue.config.js simply get passed into the electron builder properties. So I think where you end up specifying these properties depends on your particular setup, but I think that these properties themselves should be the same. So maybe a solution for you would be to put this in your package.json, if you're just trying to copy over database directory, but I'm not sure.
On Windows, ngspyce currently assumes that ngspice.dll is installed inC:\Spice\bin_dll (32-bit Python) or C:\Spice64\bin_dll (64-bit Python).Go to Ngspice Download andchoose one of the packages (such as ngspice-26plus-scope-inpcom-6-64.7z)that contains ngspice.dll, and extract it to C:\.
The ICMP_PACKETS variable contains a packet list of several icmp echo-request and icmp echo-reply packets. Submit only the ICMP chksum value from the second packet in the ICMP_PACKETS list.task.submit(ICMP_PACKETS[1][ICMP].chksum)
The variable ARP_PACKETS contains an ARP request and response packets. The ARP response (the second packet) has 3 incorrect fields in the ARP layer. Correct the second packet in ARP_PACKETS to be a proper ARP response and then task.submit(ARP_PACKETS) for inspection.ARP_PACKETS[1][ARP].op=0x2 # turn this into an is-at response ARP_PACKETS[1][ARP].hwsrc = '00:13:46:0b:22:ba' # get the src from the Ethernet header ARP_PACKETS[1][ARP].hwdst = '00:16:ce:6e:8b:24' # taken from the original request's Ethernet header task.submit(ARP_PACKETS)
Philip wrote:"So I was thinking more about say, having a package-to-be-uninstalled extracted by mxe-octave, maybe have it patched if patch files exist, and then in the tmp- subdir run 'make uninstall', followed by deleting the installed-packages/ entry. Something along those lines."I don't think we can count on packages to have working "make uninstall" targets. But we could try to keep a list of files installed for each package and add a step to remove them before building and installing the package again. We could also keep the actual installed files in a separate archive so they could be quickly reinstalled after a "make clean" if there have been no changes in the package or its dependencies. But that starts to look like a package management system...
Works OK with Qt back to 5.14.2.Yesterday I upgraded one of my Linux boxes to Mageia 8, which includes Qt 5.15.2, and guess what: now the problem exists there :-([OT]No discussion about mxe-octave's intended purpose. But as it stands it's remarkably flexible. In the past I have fiddled quite a bit with mxe-octave, it has many unexpected "potentials".In my perception package managers work primarily for compiled/prebuilt packages, a situation where dependencies are vital and fairly fragile. mxe-octave however works with source packages, implying dependencies should be resolved more easily & the build process is more robust.The dependencies in the various .mk files seem to be reasonably complete, AFAICS 'make ' picks up changed packages and dependencies as it should. E.g., just delete a basic building block entry in installed-packages/, type 'make zipdist' and watch the dependency build circus unfold.So I was thinking more about say, having a package-to-be-uninstalled extracted by mxe-octave, maybe have it patched if patch files exist, and then in the tmp- subdir run 'make uninstall', followed by deleting the installed-packages/ entry. Something along those lines.Undoubtedly there'll be snags to be sorted out; no reason to not try to get it working.BTW, thinking of it, a step I mentioned above (deleting the pertinent installed-packages/ entries) might be exactly what I forgot last time. But I'm unsure if that was the fatal blow.
OT: IIUC, MXE Octave was never thought to manage different versions of the same package. It's designed to easily allow (cross-)building of a set of packages without depending too much on any tools or dependencies installed on the build system. And does a good job at that task.It doesn't have a package manager. So once a package was built and installed there is no (standard) way of uninstalling that package. It doesn't include any rules for the various upgrade and downgrade scenarios (and I'd say that would be out of scope for such a project).Some version changes might work "accidentally" (because all files from the installation of the previous version are overwritten). But there's no guarantee for that.Adding a package manager to MXE Octave would be a huge undertaking (speaking of time and energy). That would basically require a re-design of how MXE Octave is working at the moment.
@Markus: you were right, after make clean (that I typed too quickly) an overnight build produced an mxe-octave build w/o errors. So that issue of comment #39 has been solved.I could as well have started a completely new mxe-octave, everything got built again. There must be a more elegant way to change versions of dependencies w/o rebuilding the lot. I simply don't have fast HW, and apart from that I find it a waste of time, energy and e.g., CO2 emissions for rebuilding things (non-dependers on Qt) that need not be rebuilt in the first place.That build now yields 3 new FAILs: a FAIL/REGRESSION in pathdef.m, FAIL in help.cc-tst and FAIL in bug38691.cc-tst.Plus the spreadsheet tests (spsh_test.m) in the io package now fail for the oct interface.I'll look into those later.
With a 6.1.1 nightly (octave-6.1.1_2021-02-05-00-40-w64-64.7z) I see the same issue, both at home & at work.I have several other Octave installations (5.2.0, 6.1.0, two 7.0.0), could those interfere through the settings file(s)?I had no chance yet to crossbuild with Qt 5.14; hopefully tonight.
ZX Spectrum Sound Chip Emulator (Ay_Emul) is a Windows and Linux program developed for playing music for the AY-3-8912 sound chip (or the analogous AY-3-8910 and YM2149F). Ay_Emul emulates these sound chips so you do not need the real ones. Ay_Emul can also emulate ZX Spectrum's beeper sound, and playback CD digital audio tracks and MIDI files as well. The optional BASS library by Ian Luck can be used for playing various additional formats like MP3 and MOD.Ay_Emul can play files of the following types:Dumps (or logs) of sound chip registers recorded in many computers' emulators:OUT (produced by a ZX Spectrum emulator 'Z80' v3.xx by G.A. Lunter);PSG (produced by a ZX Spectrum emulator 'Z80 Stealth' by Mr.Kirill, and in many other emulators);EPSG (recorded in a ZX Spectrum emulator 'Z80 Stealth');YM ('StSound Project' by Leonard/Oxygen files; the supported subtypes are YM2, YM3, YM3b, YM5 and YM6);VTX (files made with 'Vortex Project' by V_Soft);ZXAY (custom-made for Ay_Emul).Popular ZX Spectrum musical editors' module formats:ST1: Sound Tracker v1.xx non-compiled;AY type ST11: Sound Tracker v1.1 non-compiled, an analog of ST1;STC, ZXS: Sound Tracker v1.xx, Super Sonic v1.xx;ST3: STC recompiled (in KSA's S.T. Music's Recompiler);PSC: Pro Sound Creator v1.xx;AS0, ASC: ASC Sound Master v0.xx-2.xx;PT1, PT2, PT3: Pro Tracker v1.xx-3.xx, Vortex Tracker II v1.0;STF: Sound Tracker Pro non-compiled;STP: Sound Tracker Pro;FTC: Fast Tracker v1.xx;FLS: Flash Tracker;SQT: SQ-Tracker;GTR: Global Tracker v1.x;FXM: Fuxoft AY Language;AY type AMAD: Amadeus modules, analogous to FXM;PSM: Pro Sound Maker.ZX Spectrum, Atari ST/STe or Amstrad CPC's memory dumps which include the player for Z80 or MC68000 processors:AY type EMUL (DeliAY and AYPlay project files);AYM (RDOSPLAY project files);SNDH (Atari ST or Atari STe music files).CD audio tracks (CDA). Ay_Emul can work with several CD drives, and also with disks containing not only audio tracks.MIDI files:MID, MIDI: MIDI standard format;RMI: MID files wrapped in the RIFF container;KAR: standard MID files with song texts for karaoke;XMI: Miles Design XMIDI format.Files played by BASS library:MP3, MP2, MP1: MPEG-1 encoded waveform sound recording;OGG: Vorbis-encoded audio;WAV: any codecs of PCM audio that are installed in the system;WMA: Windows Media encoded audio (via basswma extension);APE: Monkey's Audio records (via bass_ape extension);FLAC: Free Lossless Audio Codec audio (via bassflac extension);WV: WavPack audio (via basswv extension);AC3: multichannel Dolby AC3 encoded audio;AAC: Advanced Audio Coding records;M4A, MP4: MPEG-4 wrapped audio (Advanced Audio Coding, Apple Lossless Audio Codec)DFF, DSF: Direct Stream Digital (Sony/Philips audio format)MO3: modules with MP3/OGG encoded samples;IT: Impulse Tracker;XM: Fast Tracker 2;S3M: Scream Tracker 3;MTM: MultiTracker;MOD: Sound/Noise/Star/Pro/FastTracker (and many more) module format;UMX: Unreal Tournament music package;HTTP:// and FTP:// shoutcast streams (internet radio, etc.).Any two of the majority of tracker modules listed within item 2 can be replayed simultaneously in Turbo Sound mode (TS, a device for ZX Spectrum with two ordinary sound chips onboard). The dedicated TS format of PT 3.7+ is also supported.For SNDH playback, MFP, DMA-Sound timers and some TOS functions are emulated. The MC68000 emulation uses the Starscream 680x0 emulation library by Neill Corlett (corlett@elwha.nrrc.ncsu.edu). Also supported is the SNDH known music durations database by Benjamin Gerard, imported from timedb.inc.h. To install or update it, just place the timedb.inc.h file in the main folder of Ay_Emul, and sndhtimedb will be generated/regenerated at next startup. The .h file can be downloaded from the sc68 project sources.Ay_Emul supports Winamp playlist files (M3U, M3U8), XMPlay (PLS) and its own format, AYL, as well as CUE sheets for sound streams. AYL can contain full info about each item.Ay_Emul can be used as a powerful tool for working with AY/YM data files. The built-in Speccy music ripper can find and extract modules of many ZX Spectrum music editors in any non-compressed source data. Ay_Emul can convert modules to WAV, ZXAY, VTX, YM6 or PSG formats. Ay_Emul can playback digital sound stored in OUT, ZXAY, EPSG, AY or AYM files. Beeper music in AY and AYM formats is supported too. Ay_Emul can reproduce special effects used by Atari ST musicians and stored in YM2, YM5 and YM6 formats.The skin files can change the look of Ay_Emul's main window.BASS library is only loaded immediately before playing a corresponding file and unloaded right after the playback stops.System requirements: at least Windows XP or Linux; a 80386 or greater compatible CPU is required to run the software; for playback a sound card is needed that supports 8 or 16 bit Stereo or Mono digital sound at any sample frequency in the range of 8000 to 300000 Hz and a powerful processor (by default, Ay_Emul uses a special filter to improve the quality of sound chip and beeper emulation). The requirements for playing the BASS-supported file types are DirectX 3 or above (in Windows), for MOD music a processor with MMX support too.DistributionAy_Emul is distributed as archive files that contain the executable file, BASS libraries, interface translations, skins and documentation (for Windows and Linux, 32- and 64-bit, four archives in total) and an archive with Ay_Emul's source code and other required files needed to build the executable and its help system. You can download the source code from the For Developers section. 041b061a72