DNU publish to linux runtime from windows OS - linux

I want to publish using dnu to run on linux from a windows machine. This is required to make docker images, I know the usual practice is to push the source to linux docker and do "dnu restore", but that sounds a lengthy process, and completely against the cross-compat that the DNXCore50 is trying to offer.
The latest dnx runtime now includes a "runtime" for unix/darwin related packages to target the other operating systems. But how to run a publish command that targets linux or rather if there is a way to pull the linux dnx core in a windows machine using dnvm install coreclr??

Related

Build a Linux package of Postgresql from sources

I have a Java application using Postgres. The installer is created via Install4J for Windows and Linux.
The installer also handles the installation of Postgres on the system. So there's a Postgres package included in the installer resources. In the past EDB offered packages for Windows as well as Linux but they stopped offering the Linux packages after version 10.
Is there a way to create a package of a newer version from the sources? Should be in the style the old versions were packaged in. So that the package would work on all Linux distributions, e.g. Debian, CentOS...

How should a dotnet core command line application be installed on a Linux system

I'm maintaining a couple of .NET applications on GitHub. I've been getting requests to port them over to .NET Core so that they can be used on Linux systems. I would like to make the Linux users' life easy by providing some sort of package like NuGet that can be installed.
However I'm not aware of any conventions for where the executable files actually should live in the file system. Ideally, the binaries will be deployed in directories on the PATH, but I'm not sure what convetions dotnet Core uses when it comes to the physical locations of .NET assemblies.
Ideally, I'd like to deploy:
The main assembly, pytocs.dll
A shell script that asks the dotnet core executive to launch the tool:
#!/bin/bash
dotnet pytocs.dll "$#"
but I don't know where those two file should go.

How create build .net with MSBuild in Jenkins on Server Linux

I tried to configure jenkins that is mounted on a server with linux, is it possible to install msbuild.exe to compile a .NET application? or is it necessary for Jenkins to be on a windows server?
The .NET Core SDK can be installed on Linux and comes with a tool called dotnet which can work pretty similar to MSBuild when you run it as dotnet build.
It depends on what purpose. If it is to study, I recommend installing Jenkins on a Windows Server, then installing the .Net Framework SDK that you want to use.
If it is a productive environment, I recommend installing Jenkins Master on Linux Server and a Slave on Windows Server, then installing the .Net Framework SDK that you want to use. So you do not overload the Jenkins as you compile.
If you look at the version of the .Net Framework SDK, because if any font needs something specific, you will have to install the Microsoft Windows SDK.
For configuration see this link.

Cross-compiling in Linux Alpine targeting Ubuntu

I have a virtual machine running Alpine Linux with gcc 8.2.0, and I would like to use it as a sandbox to compile programs to be installed on an Ubuntu machine. What is the procedure for doing so? I guess I will need to perform cross-compilation, but haven't found anything about it.
You can create an Ubuntu chroot with debootstrap, and compile your sources in the chroot. I doubt there is an easy way to cross-build directly from Alpine Linux.
It is also not clear why you would want to do this. If you have packaged your sources for Debian/Ubuntu, you should use a VM for that operating system and one of the native build tools (such as pbuilder or sbuild) to build in clean build environments.

TideSDK app on Mac

I developed an app via TideSDK on OSX. I have a .app and It is working on OSX. However, you know it cannot work on linux or windows. I want to run my app on linux or windows. How can I do that?
In short, you package for each platform. As you are aware mac apps do not run on Windows and it is the same with TideSDK since you are creating something native for each platform.
TideSDK must be installed on each platform to create an executable and bundle for it.
To generate an installer for each system, you need to run commands on each system (windows / linux 32bit / linux 64bit) using tidebuilder.py on the command line.
We will have more to speak about concerning packaging quite soon that will make the task of building and distributing your apps easier. Stay tuned for updates !!

Resources