CODESYS ^{Wharfie wiki (WikiPage)}
What it is Why to use it How to get it Use it on Linux [[include IndexMain (already included)] What it is CODESYS is an independent programming tool for PLCs. It consists of a programming tool, which is running under Windows, and a runtime, which can run on a real PLC or an open Linux Device, like the Raspberry Pi. Why to use it The glue for hobbyists is, that the programming system is free and the runtime is available as a 2h demo. There are generally a few major advantaes of using CODESYS over using C, python or s.th. similar: It is by far easier to access I/Os The graphical languages are easier to understand You can use an easy to use WebVisu You can easily use secure OPCUA communication to exchange variables through the internet For me, the easy I/O access and connectivity is key. How to get it To get CODESYS, you need to register yourself for free at http://store.codesys.com. After the registration you can download the programming system. Use it on Linux With some minor limitations, the programming system is running in Wine. But, as SVN and therefore cforge are not working, it has only few use cases at the moment, where it makes sense. For example, you place your project additionally on a network share to work on Linux and Windows in parallel. Then you can uae Linux for debugging and Windows to commit it in the end. For those of you, who don't have a Windows system available, you can use a trail VM from microsoft here: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ hints Please make sure that you save your projects and stuff outside of the VM when using the trail version. If you use "bridged" networking, you can easily scan your devices. Otherwhise you might need to enter the IP address in the "communication" dialog.
Last updated: 2018-12-23

Raspberry Pi ^{Wharfie wiki (WikiPage)}
Raspberry Pi Zero W + CODESYS Step 1: Download Wharfie Step 2: Install Wharfie Step 3: Configure the Image Step 4: Build the Image Step 5: Copy the image to the SD card [[include IndexMain (already included)] Raspberry Pi Zero W + CODESYS Running CODESYS on the Raspberry Pi Zero W with Wharfie is very easy. The folder "examples/CODESYS" contains a sample Wharfile which will install Debian, configure the network and even download and install CODESYS. You just need to follow the following few steps... Step 1: Download Wharfie Go to "Code" and Download "Wharfie" using SVN or using the "Download Snapshot" feature. svn checkout svn checkout --username=XXX https://forge.codesys.com/svn/tol,wharfie,code/ wharfie Step 2: Install Wharfie Go to your newly downloaded folder and execute the "install.sh" script as root. cd wharfie sudo ./install.sh Step 3: Configure the Image Enter your ESSID and Password to examples/common/files/wpa_supplicant.conf nano examples/common/files/wpa_supplicant.conf Replace <id> and <password> with the real ID and real password of your wireless access point.</password></id> network={ ssid="<id>" psk="<password>" key_mgmt=WPA-PSK } Step 4: Build the Image Enter the CODESYS example directory and let Wharfie build it. cd examples/CODESYS wharfie Step 5: Copy the image to the SD card I assume that you have done this already once. Please make sure, that you use the correct device name, as you will damage your operating system otherwise. sudo dd if=rpi.img of=/dev/sdX status=progress Note, you need to replace /dev/sdX with the device name of your SD card.
Last updated: 2018-02-25

IndexMain ^{Wharfie wiki (WikiPage)}
Documentation Commands Tutorials Quickstart CODESYS Raspberry Pi
Last updated: 2018-03-01

Command Reference ^{Wharfie wiki (WikiPage)}
Target Commands FROM debootstrap archive remote archive RUN Install software with apt-get Add user and set password CMD LICENSE SOURCE TOOLCHAIN Host commands RUN HOST ADD COPY Common Commands ENV INCLUDE (Draft - not implemented, yet) [[include IndexMain (already included)] Target Commands Target commands are executed within the root filesystem which we are just building. This concept is similar to the one of Docker. The key benefit of using those commands is, that it is very natural. You can automate virtually every command, which you would use to configure the system manually in your terminal. When you build a system for a foreign architecture, Wharfie uses Qemu to.be able to execute the commands on your x86 host. FROM The from directive refers the starting point of your root filesystem. Before you can execute any command inside of your new root filesystem, you obviously need a basic root filesystem. This can be obtained from several sources. debootstrap You just need to specify the architecture and the debian version in the following syntax: debian_<architecture>_<version> For example: FROM debian_armel_stretch archive You can specify a tar archive. For example, this can be a build artifact from previous build step. For example: FROM iotbase.tar remote archive Beside tar, wharfie supports a few more archive formats, which can be handy to use external sources as a starting point for your image. So, the following formats are supported: a img * zip You can pass options for the different formats, separated from the Url by a pipe symbol. For example: FROM https://downloads.raspberrypi.org/raspbian_lite_latest|img=p1|format=tar The format specifies, where to stop with the extract. In the FROM statement this should always be a tar archive. But when this syntax is used in an ADD statement, you might leave this empty and pass an option like "|tar=etc/fstab" to extract a single file. At first it might be a bit confusing why the extraction of an image results in a tar archive. But wharfie treats every folder as a tar archive. Thats the way how a folder is passed to another build step, including all permissions, attributes and links. The parameter "img=p1" from the example specifies, that we want to extract partition number 1 from the image file. In this case partition number 0 is the boot partition, and number 1 contains the root filesystem. RUN Run gets exactly one argument. This is the command, which should be executed on the targets root filesystem. This command can be multiline. For example: RUN apt-get install -y psutils \ openssh-server ... The Backslash () at the end of the line indicates, that the command continues in the next line. Install software with apt-get If you want to install a new software on your target image, you most likely want to use apt. To avoid apt and dpkg from requesting inputs from the user, you can pass "-y" to apt-get. For example: RUN apt-get install -y tzdata In case you want to deviate from the default, you might want to use dpkg-reconfigure after the installation. RUN echo Antarctica/Mawson > /etc/timezone && dpkg-reconfigure -f noninteractive tzdata Add user and set password An easy, non-interactive way to add a user and set his password is to use the tools "useradd" and "chpasswd". This example adds the user "wharfie" with the password "secret": RUN useradd -ms /bin/bash wharfie; echo "wharfie:secret" | chpasswd; CMD This command comes from Docker. There it defines the one and only entry point of the docker container. In Wharfie it defines a command that is executed from a systems service unit. So there can be multiple commands, and they are all executed at the end of the boot process. For example: CMD ['/run.sh'] LICENSE This command is creating an archive with all the license texts of all installed packages. Note, that packages which are installed from 3rd party sources are not included in this archive. For example: LICENSE all-licenses.tar SOURCE This command is creating an archive with all debian source packages, which are currently installed in the system. Like for the license archive, this archive doesn't contain 3rd party packages. SOURCES all-sources.tar TOOLCHAIN This command exports a crosstoolchain, containing the full root filesystem of the target, as well as a cross compiler for an x86 host. It can be simply exported as a tar archive. For example: TOOLCHAIN cross-toolchain.tar If you need more host tools then just the gcc compiler, you can define those packages in an environment variable. ENV ADDITIONAL_TOOLCHAIN_PACKAGES libstdc++4.9-dev ... If you want to execute some commands in the host sysroot, before the toolchain is packed, you can do this by appending this commands to the TOOLCHAIN commad: TOOLCHAIN cross-toolchain.tar \ apt-get install -y git; \ ... Host commands RUN HOST Host commands can be used for virtually every action which don't need to be executed on the target, but where files on the host are involved. For example: prepare a bootable image of the target root filesystem download an archive and extract only parts of it compile a kernel and add it to the root filesystem ... The syntax is exactly the same as the RUN command. The commands are executed as root from the extracted target folder, which is extracted into a folder directly beside the Wharfile. ADD This action can add files, folders and archives into a root filesystem. Even files and archives from URLs are possible. Every archive will be implicitely extracted into the destination folder. For example: ADD etc.tar /etc COPY Copy acts very similar to ADD. The only differenxe is, that this command really only copies files and directories. So also archives are treated as standard files, what might be the intention in some cases. Common Commands ENV With this command, you can set global environment variables, which are accessible in every RUN or RUN HOST command. This includes environment variables of sub processes. For example: ENV DEBIAN_FRONTEND noninteractive RUN apt-get install ... INCLUDE (Draft - not implemented, yet) The include command can be used to structure your features into different Wharfiles, which can be reused in different Wharfiles. The syntax is simple, as the only parameter to the command is the path to the include file. ENV ESSID mywifi ENV PASSWORD mypass INCLUDE net/wpa.wha INCLUDE bs/rpi.wha The included files are searched locally, and only as fallback from an URL. The search URL can be specified with the command INCLUDE_URL. INCLUDE_URL http://forge.codesys.com/... INCLUDE bs/rpi.wha The default URL can be set again by calling INCLUDE_URL without a parameter. INCLUDE_URL INCLUDE bs/rpi.wha
Last updated: 2020-02-05

Ticket #1: Build as non-root user ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi Allow building as non-root user. Currently we need root, as we are using chroot. After switching to fakechroot, we have the problem of non-native target systems. Then we are using qemu through binfmt, which simply doesn't work in combination with chroot. The way how fakechroot works is preloading a wrapper library through LD_PRELOAD. So the following scenerio sounds valid: fakechroot chroot rootfs/ /bin/bash /bin/bash is a target binary, executed through binfmt. chroot itself is still a host binary. fakechroot will fixly preload it's wrapper. We would need a few things: When building a base system with debootstrap, we always need to corresponding libfakechroot.so fo the target. In my opinion this library can be stored globally in a similar manner as debian_version.mk When issuing the chroot, we need to switch LD_PRELOAD to the new folder Note: We need to check if the permissions on the files will remain the same after we switched from the host to the target library. Because the command is in fact a bit more complex: fakechroot bash -c "cd ...; tar -xf ...; chroot . ./.trg.sh; ..." So we have the files created with the host version of libchfakeroot.so and then we execute the target binaries with the target version. Not sure if we can guarantee, that they are seeing the same file permissions, as I don't know where this information is stored.Build as non-root user Wharfie 0 tickets Ticket tickets Build as non-root user 2018-03-09 15:40:55.955000 closed False 0 *anonymous Ticket #1: Build as non-root user 0 1.0 False /tol/wharfie/tickets/1/ ingo 2017-11-04 00:23:43.852000 1 1 wharfie Originally created by: labi Originally owned by: labi Allow building as non-root user. Currently we need root, as we are using chroot. After switching to fakechroot, we have the problem of non-native target systems. Then we are using qemu through binfmt, which simply doesn't work in combination with chroot. The way how fakechroot works is preloading a wrapper library through LD_PRELOAD. So the following scenerio sounds valid: fakechroot chroot rootfs/ /bin/bash /bin/bash is a target binary, executed through binfmt. chroot itself is still a host binary. fakechroot will fixly preload it's wrapper. We would need a few things: When building a base system with debootstrap, we always need to corresponding libfakechroot.so fo the target. In my opinion this library can be stored globally in a similar manner as debian_version.mk When issuing the chroot, we need to switch LD_PRELOAD to the new folder Note: We need to check if the permissions on the files will remain the same after we switched from the host to the target library. Because the command is in fact a bit more complex: fakechroot bash -c "cd ...; tar -xf ...; chroot . ./.trg.sh; ..." So we have the files created with the host version of libchfakeroot.so and then we execute the target binaries with the target version. Not sure if we can guarantee, that they are seeing the same file permissions, as I don't know where this information is stored. False False 1
Last updated: 2018-03-09

Ticket #4: Abort on error ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi Currently on errors of the host or target commands, the build doesn't fail.Abort on error Wharfie 0 tickets Ticket tickets Abort on error 2017-11-14 22:31:28.093000 closed False 0 *anonymous Ticket #4: Abort on error 0 1.0 False /tol/wharfie/tickets/4/ None 2017-11-04 00:37:59.268000 4 4 wharfie Originally created by: labi Originally owned by: labi Currently on errors of the host or target commands, the build doesn't fail. False False 0
Last updated: 2017-11-14

Ticket #6: Support URLs in FROM and ADD ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi Support at least http:// and ftp:// as protocols. Think about SVN / GITSupport URLs in FROM and ADD Wharfie 0 tickets Ticket tickets Support URLs in FROM and ADD 2017-11-19 01:19:59.342000 closed False 0 *anonymous Ticket #6: Support URLs in FROM and ADD 0 1.0 False /tol/wharfie/tickets/6/ None 2017-11-16 08:14:10.439000 6 6 wharfie Originally created by: labi Originally owned by: labi Support at least http:// and ftp:// as protocols. Think about SVN / GIT False False 0
Last updated: 2017-11-19

Ticket #7: Support the commands COPY and ENTRYPOINT ^{Wharfie tickets (Ticket)}
Originally created by: labi Support the commands COPY and ENTRYPOINT Wharfie 0 tickets Ticket tickets Support the commands COPY and ENTRYPOINT 2018-08-31 23:42:00.995000 closed False 0 *anonymous Ticket #7: Support the commands COPY and ENTRYPOINT 0 1.0 False /tol/wharfie/tickets/7/ None 2017-11-16 08:14:33.434000 7 7 wharfie Originally created by: labi False False 2
Last updated: 2018-08-31

Ticket #5: No parse error if wrong commands are used ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi The simple regex based parser of wharfie doesn't throw an error when it doesn't recognize a command, but simply ignores it.No parse error if wrong commands are used Wharfie 0 tickets Ticket tickets No parse error if wrong commands are used 2017-11-14 21:04:35.752000 closed False 0 *anonymous Ticket #5: No parse error if wrong commands are used 0 1.0 False /tol/wharfie/tickets/5/ None 2017-11-07 08:39:19.682000 5 5 wharfie Originally created by: labi Originally owned by: labi The simple regex based parser of wharfie doesn't throw an error when it doesn't recognize a command, but simply ignores it. False False 0
Last updated: 2017-11-14

Ticket #8: Use incremental/multi-level build for image data ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi as we are using tar, we can use the multi level backup and restore concept. It supports already differential file backups, including deletion of files. What we need is "*.snar" file, recording the changes. As the snar file will become corrupted when we rebuild older files, we need to track the state of the snar file for each layer. In practice that means, that every build target has from now on, an additional snar file as its output, as well as an additional snar file as input. The FROM target doesn't produce a snar file. So it is automatically the level-0 backup. In fact I believe that packing should not make big trouble, as we can always just check if a a snar is there. if yes, use it. If no, leave it and create a level-0 backup. The extract of the archives on the other hand is a bit more tricky. We now need the info about all archives, which are involved, starting from the level-0 backup. The safest way will be to track this transparently in the makefile generation process, as we are also managing the archives there.Use incremental/multi-level build for image data Wharfie 0 tickets Ticket tickets Use incremental/multi-level build for image data 2017-11-21 22:08:10.097000 closed False 0 *anonymous Ticket #8: Use incremental/multi-level build for image data 0 1.0 False /tol/wharfie/tickets/8/ None 2017-11-19 01:37:40.879000 8 8 wharfie Originally created by: labi Originally owned by: labi as we are using tar, we can use the multi level backup and restore concept. It supports already differential file backups, including deletion of files. What we need is "*.snar" file, recording the changes. As the snar file will become corrupted when we rebuild older files, we need to track the state of the snar file for each layer. In practice that means, that every build target has from now on, an additional snar file as its output, as well as an additional snar file as input. The FROM target doesn't produce a snar file. So it is automatically the level-0 backup. In fact I believe that packing should not make big trouble, as we can always just check if a a snar is there. if yes, use it. If no, leave it and create a level-0 backup. The extract of the archives on the other hand is a bit more tricky. We now need the info about all archives, which are involved, starting from the level-0 backup. The safest way will be to track this transparently in the makefile generation process, as we are also managing the archives there. False False 0
Last updated: 2017-11-21

Ticket #11: debootstrap doesn't work on stretch ^{Wharfie tickets (Ticket)}
Originally created by: labi Currently we are facing the problem with stretch, that debootstrap doesn't want to build. Most likely its because of this error: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838388debootstrap doesn't work on stretch Wharfie 0 tickets Ticket tickets debootstrap doesn't work on stretch 2019-04-05 11:39:39.456000 closed False 0 *anonymous Ticket #11: debootstrap doesn't work on stretch 0 1.0 False /tol/wharfie/tickets/11/ ingo 2018-02-13 16:46:33.461000 11 11 wharfie Originally created by: labi Currently we are facing the problem with stretch, that debootstrap doesn't want to build. Most likely its because of this error: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838388 False False 1
Last updated: 2019-04-05

Ticket #10: Toolchains are not building ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi There are actually two errors: 1) debian_version.mk is not included in the same run as it is created Therefore an initial build fails with "can't cd to http://ftp.debian.org", while a second run (w/o clean) progresses further. 2) Then it fails with "Makefile:34: recipe for target '32323D8C.piling.tar' failed" This is most likely a problem which occurs after hardening the makerules, so that they throw an error on all commands that fail. And it is a problem which is not in the toolchain rule in wharfie.mk, but in the generated rule which combines the sysroots of the host and the target.Toolchains are not building Wharfie 0 tickets Ticket tickets Toolchains are not building 2018-02-01 23:39:07.967000 closed False 0 *anonymous Ticket #10: Toolchains are not building 0 1.0 False /tol/wharfie/tickets/10/ None 2018-02-01 22:24:25.176000 10 10 Core wharfie Originally created by: labi Originally owned by: labi There are actually two errors: 1) debian_version.mk is not included in the same run as it is created Therefore an initial build fails with "can't cd to http://ftp.debian.org", while a second run (w/o clean) progresses further. 2) Then it fails with "Makefile:34: recipe for target '32323D8C.piling.tar' failed" This is most likely a problem which occurs after hardening the makerules, so that they throw an error on all commands that fail. And it is a problem which is not in the toolchain rule in wharfie.mk, but in the generated rule which combines the sysroots of the host and the target. False False 0
Last updated: 2018-02-01

Ticket #3: Recreate SSH key at boot ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi Currently the SSH key is created during installation. So it is the same for all targets where the created root filesystem will be rolled out.Recreate SSH key at boot Wharfie 0 tickets Ticket tickets Recreate SSH key at boot 2019-04-05 11:40:41.916000 closed False 0 *anonymous Ticket #3: Recreate SSH key at boot 0 1.0 False /tol/wharfie/tickets/3/ ingo 2017-11-04 00:33:17.379000 3 3 examples wharfie Originally created by: labi Originally owned by: labi Currently the SSH key is created during installation. So it is the same for all targets where the created root filesystem will be rolled out. False False 1
Last updated: 2019-04-05

Ticket #2: Read Only Root ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi Create the possibility to boot a device read-only and commit changes with a special command. The exact solution is not clear, yet. But it has to be as portable as possible.Read Only Root Wharfie 0 tickets Ticket tickets Read Only Root 2017-11-04 00:26:25.414000 open False 0 *anonymous Ticket #2: Read Only Root 0 1.0 False /tol/wharfie/tickets/2/ None 2017-11-04 00:26:25.153000 2 2 examples wharfie Originally created by: labi Originally owned by: labi Create the possibility to boot a device read-only and commit changes with a special command. The exact solution is not clear, yet. But it has to be as portable as possible. False False 0
Last updated: 2017-11-04

Ticket #9: Support CODESYS with self-contained raspbian libraries ^{Wharfie tickets (Ticket)}
Originally created by: labi Originally owned by: labi CODESYS was compiled for raspbian. Sadly raspbian is incompatible with a standard debian, as it uses a different ABI. It uses the hardfloat ABI, but compatible with ARMv6. If you have a RPI Zero / 1 / ..., which is based on ARMv6, you can only use the armel ABI from debian. As those are incompatible, it causes problems with floating point calculations. The solution is to use the glibc and gcc libraries from Raspbian, but solely with codesys. This can be achieved by changing the interpreter path and the rpath to a place, where our raspbian libraries are found. We will place them under /opt/codesys/lib/Support CODESYS with self-contained raspbian libraries Wharfie 0 tickets Ticket tickets Support CODESYS with self-contained raspbian libraries 2018-01-05 13:46:06.813000 closed False 0 *anonymous Ticket #9: Support CODESYS with self-contained raspbian libraries 0 1.0 False /tol/wharfie/tickets/9/ None 2018-01-05 13:44:37.791000 9 9 examples wharfie Originally created by: labi Originally owned by: labi CODESYS was compiled for raspbian. Sadly raspbian is incompatible with a standard debian, as it uses a different ABI. It uses the hardfloat ABI, but compatible with ARMv6. If you have a RPI Zero / 1 / ..., which is based on ARMv6, you can only use the armel ABI from debian. As those are incompatible, it causes problems with floating point calculations. The solution is to use the glibc and gcc libraries from Raspbian, but solely with codesys. This can be achieved by changing the interpreter path and the rpath to a place, where our raspbian libraries are found. We will place them under /opt/codesys/lib/ False False 0
Last updated: 2018-01-05

Ticket #12: Suport the command INCLUDE ^{Wharfie tickets (Ticket)}
Implement the new command INCLUDE, and INCLUDEDIR. While include dir explicitely supports URLs.Suport the command INCLUDE Wharfie 0 tickets Ticket tickets Suport the command INCLUDE 2018-03-10 13:16:07.594000 open False 0 ingo Ticket #12: Suport the command INCLUDE 0 1.0 False /tol/wharfie/tickets/12/ None 2018-02-25 17:14:54.435000 None 12 wharfie Implement the new command INCLUDE, and INCLUDEDIR. While include dir explicitely supports URLs. False False 1
Last updated: 2018-03-10

Ticket #13: g++ in env.sh is wrong ^{Wharfie tickets (Ticket)}
CXX=$${COMPILE_PREFIX}cpp in wharfie.mk should be CXX=$${COMPILE_PREFIX}g++g++ in env.sh is wrong Wharfie 0 tickets Ticket tickets g++ in env.sh is wrong 2019-04-03 06:40:15.936000 closed False 0 erichspitzweg Ticket #13: g++ in env.sh is wrong 0 1.0 False /tol/wharfie/tickets/13/ ingo 2019-04-02 11:14:56.739000 None 13 wharfie CXX=$${COMPILE_PREFIX}cpp in wharfie.mk should be CXX=$${COMPILE_PREFIX}g++ False False 2
Last updated: 2019-04-03

Ticket #14: error while apt-get install: "... -y was used without --allow-unauthenticated" ^{Wharfie tickets (Ticket)}
Error from apt-get E: There were unauthenticated packages and -y was used without --allow-unauthenticated missing "--allow-unauthenticated" in case of "-y" at all "apt-get install --allow-unauthenticated -y ..." error while apt-get install: "... -y was used without --allow-unauthenticated" Wharfie 0 tickets Ticket tickets error while apt-get install: "... -y was used without --allow-unauthenticated" 2019-04-08 12:55:15.616000 closed False 0 erichspitzweg Ticket #14: error while apt-get install: "... -y was used without --allow-unauthenticated" 0 1.0 False /tol/wharfie/tickets/14/ None 2019-04-03 14:14:12.446000 None 14 wharfie Error from apt-get E: There were unauthenticated packages and -y was used without --allow-unauthenticated missing "--allow-unauthenticated" in case of "-y" at all "apt-get install --allow-unauthenticated -y ..." False False 2
Last updated: 2019-04-08

Ticket #15: g++ missing in cross toolchain ^{Wharfie tickets (Ticket)}
gcc for cross compilation is included in toolchain, but g++ is missing. g++ missing in cross toolchain Wharfie 0 tickets Ticket tickets g++ missing in cross toolchain 2019-04-07 18:56:32.692000 closed False 0 erichspitzweg Ticket #15: g++ missing in cross toolchain 0 1.0 False /tol/wharfie/tickets/15/ ingo 2019-04-03 14:34:31.559000 None 15 wharfie gcc for cross compilation is included in toolchain, but g++ is missing. False False 2
Last updated: 2019-04-07

Ticket #16: TOOLCHAIN commands are executed in target instead of host sysroot ^{Wharfie tickets (Ticket)}
TOOLCHAIN commands are executed in target instead of host sysroot Wharfie 0 tickets Ticket tickets TOOLCHAIN commands are executed in target instead of host sysroot 2020-08-04 14:25:50.710000 closed False 0 ingo Ticket #16: TOOLCHAIN commands are executed in target instead of host sysroot 0 1.0 False /tol/wharfie/tickets/16/ None 2020-08-03 10:15:13.777000 None 16 wharfie False False 4
Last updated: 2020-08-04

Ticket #17: substitute debian_versions.mk and push this info into the central Makefile ^{Wharfie tickets (Ticket)}
The toolchain commands are using this file, and it would be nice if the info is scanned initially from the Wharfile and then generated fixly as part of the central Makefile. Otherwise, when you have a debian_*.tar file already in place, but you are missing the debian_version.mk, it just gives a weired error, as the architecture and versions are not known in the TOOLCHAIN command.substitute debian_versions.mk and push this info into the central Makefile Wharfie 0 tickets Ticket tickets substitute debian_versions.mk and push this info into the central Makefile 2020-08-03 10:20:00.496000 open False 0 ingo Ticket #17: substitute debian_versions.mk and push this info into the central Makefile 0 1.0 False /tol/wharfie/tickets/17/ None 2020-08-03 10:20:00.424000 None 17 wharfie The toolchain commands are using this file, and it would be nice if the info is scanned initially from the Wharfile and then generated fixly as part of the central Makefile. Otherwise, when you have a debian_*.tar file already in place, but you are missing the debian_version.mk, it just gives a weired error, as the architecture and versions are not known in the TOOLCHAIN command. False False 1
Last updated: 2020-08-03

Post by ingo on #7 Support the commands COPY and ENTRYPOINT ^{Wharfie tickets (Post)}
summary: Support the commands COPY, USER and CMD --> Support the commands COPY and CMD Description has changed: Diff: status: open --> closed
Last updated: 2018-08-31

Post by ingo on #11 debootstrap doesn't work on stretch ^{Wharfie tickets (Post)}
A current Workaround is the use of the non-root mode w/ qemu, as it will use a jessie image for building.
Last updated: 2019-04-05

Post by ingo on #7 Support the commands COPY and ENTRYPOINT ^{Wharfie tickets (Post)}
summary: Support the commands COPY and CMD --> Support the commands COPY and ENTRYPOINT
Last updated: 2018-08-31

Post by *anonymous on Ticket 6 discussion ^{Wharfie tickets (Post)}
Originally by: labi status: open --> closed assigned_to: Ingo
Last updated: 2018-02-24

Sort by relevance or date