|Sulaiman AlIbrahim f30481115b Changed company name in legal notices||1 year ago|
|container-files||1 year ago|
|test-crate||1 year ago|
|Dockerfile||1 year ago|
|Makefile||1 year ago|
|README.md||1 year ago|
|build-image.sh||1 year ago|
|gpl-3.0.txt||1 year ago|
|lgpl-3.0.txt||1 year ago|
|signatures.sha256||1 year ago|
|signatures.sha256.1E906D4F04AFD7A4E0D09080B09F435DBFDEF8B5.asc||1 year ago|
|signatures.sha384||1 year ago|
|signatures.sha384.1E906D4F04AFD7A4E0D09080B09F435DBFDEF8B5.asc||1 year ago|
This Linux container provides a self-contained version of
cargo that is
capable of compiling and running Rust projects for
This container uses wine to automatically run compiled executables
and test harnesses.
This container is designed to act as a drop in version of cargo that
x86_64-pc-windows-gnu. Aside from automatically injecting
--target flag and the caveats listed bellow, this container
supports common usage patterns such as:
CONTAINER build --release CONTAINER run CONTAINER test TEST-NAME
test sub-commands run binaries in wine without user intervention.
To obtain this container, you have two options:
Dockerhub containers are tied to the version of Rust they ship.
The major and minor components of the tag correspond directly to their Rust counterparts.
The patch component is independent of Rust’s version, and is used to reflect the version
of the container instead. For example,
kutometa/cargo-x86_64-windows-wine:1.40.1 is the second version
of an image that ships Rust version 1.40.X.
Instructions on how to build the container are detailed bellow. Instructions on how to run the container follow.
This container is built on top of Debian 9 “Stretch”. During the build process, several remote resources must be fetched from the internet. Each of these resource are verified against a prepinned public key or a prepinned cryptographic hash.
These remote resources are:
To build this container, you have two options. You can either use
docker build or
If you use
make, the resulting container image is automatically
kutometa/cargo-x86_64-windows-wine:local and tested.
If docker was used to build the container locally, the container can be invoked by issuing the following command:
docker run -ti --rm \ -v <CRATE-DIR>:/crate \ kutometa/cargo-x86_64-windows-wine:local \ <CARGO-CMD> \ <ARGS> ...
Alternatively, if the container was built using make, a launcher script can be installed on your system using
make install. Once installed,
the container can be launched by running
cargo-x86_64-windows-wine-local build cargo-x86_64-windows-wine-local test
docker is allocated a pseudoterminal (pty),
an extra carriage return (U+0D) is inserted before the end of each line. Do
-t if unmodified io streams are required.
This container can only target
جميع الحقوق المتعلقة في هذا العمل محفوظة لشركة كوتوميتا لبرمجة وتشغيل الكمبيوتر وتصميم وإدارة مواقع الإنترنت (ش.ش.و). سنة النشر ٢٠٢٠.
Copyright © 2020 Kutometa SPC, Kuwait. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of the third version of the GNU Lesser General Public License as published by the Free Software Foundation.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this work; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.