I am trying to install masm32 in an automated and headless fashion. Specifically, I am trying to setup a Windows Docker container that contains masm32 to build asm tools. Is this possible with the masm32 installer? Or can I assume if I install masm32 on my Windows 10 system that I can safely zip up the installation folder and drop it into a Docker container?
Thanks!
Once you have Masm32 installed on any drive, you can copy it to any other drive including USB drives. Does this help answer your question? I have no clue what headless or docker mean.
Quote from: sudoku on May 01, 2024, 02:25:46 AMI have no clue what headless or docker mean.
https://www.docker.com/resources/what-container/ (https://www.docker.com/resources/what-container/)
QuoteA container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
Container images become containers at runtime and in the case of Docker containers – images become containers when they run on Docker Engine. Available for both Linux and Windows-based applications, containerized software will always run the same, regardless of the infrastructure. Containers isolate software from its environment and ensure that it works uniformly despite differences for instance between development and staging.
Clear as mud. Care to explain this in non-market-ese? What does this stuff actually do?
Quote from: NoCforMe on May 01, 2024, 04:14:04 AMClear as mud. Care to explain this in non-market-ese? What does this stuff actually do?
What's unclear? It's similar to Application Virtualization. Same, same but different.
How is Docker different from a virtual machine? (https://stackoverflow.com/questions/16047306/how-is-docker-different-from-a-virtual-machine)
Seems like some kind of virtualization or virtual machine. I would think that anything ran in it would run slower.
In either case I could live the rest of my life, without ever using it.
Well, yes, it seems to be some kind of virtual machine. Except that one comment in the thread that Fearless linked says
QuoteDocker isn't a virtual machine - it is a configuration management tool.
But in any case, I still have no idea what this is all really about. All the descriptions I read about this are written in jargon-ese and don't explain anything unless one already understands the concept.
So can someone explain
in plain English what this is? and why I'd want to use it?
The Masm32 SDK installation (https://www.jj2007.eu/Masm32_Tips_Tricks_and_Traps.htm) is indeed a bit clumsy. It builds 158kB of \Masm32\m32lib\masm32.lib from 550kB of sources (in the same folder). MasmBasic (http://masm32.com/board/index.php?topic=94.0) is easier to install, but first, it builds on the SDK and second, Windows will still show you some misleading dialogs trying to discourage you from installing a non-Micros*t product :cool:
The good news is you have to go only once through the Masm32 SDK installation :bgrin:
Still, it is not quite clear what you want:
a) a simplified, dialogless installation of the SDK (which does contain all necessary tools);
b) a kind of VM or sandbox from where to build Masm projects?
Fasm has a docker container: https://github.com/guitmz/fasm-docker (https://github.com/guitmz/fasm-docker)
Which you can use for CI/CD
QuoteCI/CD is the combined practices of continuous integration and continuous delivery or, less often, continuous deployment.
Imagine a github repo that can automatically build and package your releases every time you commit to it and then you will understand that a docker container can be useful for launching on a machine with all the appropriate Compilers, Tools and SDKs (Visual Studio, Win10 SDK for example but could be any development environment on any OS that the container is based on) installed and ready to deploy, along with custom scripts to automate the process and build the project and then report if the build was successful or failed for some reason.
Could be useful to have a UASM, WinInc and Visual Studio in a container to automate builds for projects.
Quote from: fearless on May 01, 2024, 06:24:51 AMa docker container can be useful for launching on a machine with all the appropriate Compilers, Tools and SDKs
So what is the difference to a self-extracting zip archive that "contains all the appropriate Compilers, Tools and SDKs"?
Hi rockso,
The Masm32 installation is portable. You don't need a Windows Docker container. Maybe, you could try a free tool like Sandboxie to test the Masm32 package which does not modify the registry during installation :
https://sandboxie-plus.com/downloads/ (https://sandboxie-plus.com/downloads/)
QuoteSo what is the difference to a self-extracting zip archive that "contains all the appropriate Compilers, Tools and SDKs"?
Thats the point really. For CI/CD typically the docker text config file (yaml i believe) has the instructions of what is required, deploys the OS it is to use in a VM (which can be small linux distros like linux alpine or others), downloads any dependencies and installs them, then runs any of your config/test/build scripts required. Outputs can be pushed to github repos or other online servers ready for downloads if it passes tests. The VM can be shut down and deleted after it has completed.
From that point of view its an on-demand automatic way of testing and/or building and/or deploying remotely. It can be configured to run when a commit is pushed to github for example (using actions)
If your only coding locally and uploading somewhere infrequently and not using some version control like github/gitlab/bitbucket etc then it probably isnt needed, unless you wanted to run some automated tests and builds locally of course.
Quote from: fearless on May 01, 2024, 07:03:44 AMdeploys the OS it is to use in a VM (which can be small linux distros like linux alpine or others)
The whole Masm32 SDK is around 12MB or so. What you describe sounds like gigabytes. That is an overkill IMO.
Hi Jochen,
Alpine Linux is not that bad. The 64-bit version of the installation file weights 211 Mb :
https://alpinelinux.org/downloads/ (https://alpinelinux.org/downloads/)
https://dl-cdn.alpinelinux.org/alpine/v3.19/releases/aarch64/alpine-standard-3.19.1-aarch64.iso (https://dl-cdn.alpinelinux.org/alpine/v3.19/releases/aarch64/alpine-standard-3.19.1-aarch64.iso)
QuoteSMALL
Alpine Linux is built around musl libc and busybox. This makes it small and very resource efficient. A container requires no more than 8 MB and a minimal installation to disk requires around 130 MB of storage. Not only do you get a fully-fledged Linux environment but a large selection of packages from the repository.
https://alpinelinux.org/about/ (https://alpinelinux.org/about/)
Hi Erol,
Yes, that's not bloatware. However, I doubt that you can do Windows programming on Linux Alpine. And there is talk about adding Visual Studio...
Quote from: fearless on May 01, 2024, 06:24:51 AMwith all the appropriate Compilers, Tools and SDKs (Visual Studio, Win10 SDK for example
Quote from: jj2007 on May 01, 2024, 08:32:07 AMI doubt that you can do Windows programming on Linux Alpine.
Not even running under Wine?
Most CI/CD providers have all the OS, toolchains, SDKs and compilers cached, so deploying them on a VM like a docker container doesnt really involve much downloading if any. Sure they can be configured to pull and update from latest sources from github or other locations, or they can be specifically forced to use particular versions of OS, toolchains or compilers.
Its really about convenience to automate the test, build and deploy mainly used by large companies and/or multiple coders using a source control/version control solution. But can of course be used by hobbyists/individual coders. Github and its Actions are just one example of a CI/CD provider in that sense, and they each probably offer different support for various development environments and tools.
So spinning up a docker container or VM with a specific windows OS and using a specific Visual Studio Installation and a specific version of a C/C++/C# compiler is fairly easy to do, along with any other OS and development toolchain you can think of. Its all done remotely on the CI/CD provider server. So its not really about downloading locally unless, as I mentioned in a prior post, you have specific requirements to do so for automating testing etc.
Uasm has a linux version, so could be included in a linux docker container, although I dont know how easy or hard it would be to setup and how easy it would be to compile for win x86/x64 using it - maybe someone has some knowledge of how that might be achieved.