Hi I need a manylinux1 whl distribute for some python package to work in an old server.
I found the manylinux project and installed docker.
My platform is Windows 10 and processor is Intel, so I cannot run nest virtualization in VirtualBox.
So how should I build the docker image under Windows?
Thanks a lot!
Manylinux helps to compile for different CPU architectures. It also helps to repair your wheel for a manylinux tag and makes it acceptable by PyPI.
If you're building wheels, consider porting your project to a CI environemnt, like GitHub Actions, and use CIBUILDWHEEL. It helps when you have to compile for many platforms and Python versions.
Related
Background
I have been playing around with Scenic to make a desktop app across multiple environments. While the Install dependencies for Ubuntu are outdated and don;t work for the latest LTS (v20) I was still able to figure out the packages and install it on Ubuntu Linux.
However ... there is nothing for Windows.
Questions
Does Scenic even work on Windows?
If so, what are the dependencies? What need I to install?
Answer
Unfortunately, Scenic does not run on Windows, nor can it support it.
At the time of writing of this post, I am also unaware of any plans to make it work on a Windows system.
The confirmation came from an official collaborator from the Scenic project:
https://github.com/boydm/scenic/issues/206
I recently installed the windows branch of Caffe onto my windows machine. It works fine but then we I tried running some other projects I found online they didn't work at all and gave me all kinds of errors.
I think the reason it doesn't work is because they were using a different branch of caffe, this one for instance.
Is there a fix to this problem? Can I run ssd caffe on windows somehow?
The Caffe-SSD is not a branch, but a fork of the vanilla Caffe. Compiling and using Caffe on Windows requires certain effort (e.g. pre-building some external libs, adjusting CMake config etc.), which was not done for the Caffe-SSD fork.
You need to merge the contributions from the Windows branch into the Caffe-SSD. There are some existing solutions for that (https://github.com/runhang/caffe-ssd-windows, https://github.com/gustavkkk/caffe-ssd-win, google for more), but I did not use those.
A bit of advice appreciated here before I start this. Hopefully the question will help other newbie users of nw.js as well.
I develop on a mac and I have build and deployed an HTML5 app using nw.js that runs successfully on a mac.
My question is simple. Can I build for windows and linux whilst still working from my mac, or do I need to invest in a windows machine and build it from there. Ditto for Linux.
My reason for asking is also because I read somewhere that the node modules installed in the package are not the same for each platform. I suppose you could say I have just answered my own question, but here's hoping!
The short answer is yes you can. I did (at least I have build for both Mac and Windows from Mac, I have not attempted Linux yet).
The mac build was easy. The windows build requires that you install wine (brew install wine, hopefully you installed node with brew, so brew is already on your system. If you did not, I recommend first removing node (very carefully!) and reinstalling it with brew).
Wine is required by the node build programmes (I use nw-builder-phoenix) to create the windows installer.
Wine has a few pre-requisites as well (cask, java and xquartz).
But having done all of this and re-run the build programme, it all works.
The icon format is different, .ico for windows apps and .icns for mac. They can both be generated from a .png file either using an app or a website.
Have fun.
I would like to try scidb as a replacement for hdf5. I would like to test it on my Debian laptop (no clusters) to give it a try.
Is this possible? Might be that Debian (as opposed to Ubuntu) is not supported?
I had no luck with the installation instructions. The deployment script tells that my OS is not supported. The scidb userguide says about some pre-built packages (for Ubuntu, at least). But there is no hint on how to obtain them.
SciDB is limited to RedHat / CentOS, and to Ubuntu as of the 14.9 release. Folk who want to run it on other distros generally compile from code.
Information about how to obtain the sources (as well as current documentation and community discussion) can be found on the forums here ... http://www.scidb.org/forum/. You'll need to register as a forum user.
Specifically, have a look at http://www.scidb.org/forum/viewtopic.php?f=16&t=364. There's a list of releases and links to code bundles there.
I installed SciDB several times using several ways (building from sources and installing from packages, installing the cluster version and the dev version).
Installation from packages
First, if you choose to install from packages (the easiest and fastest way), SciDB is very very sensitive about your Linux version. For example, for the last version of SciDB (14.8), if you choose to install on a Ubuntu, it has to be a Ubuntu 12.04 (and not a 14.04, a common mistake) 64 bits (meaning you have to install the AMD64 version even if you have an Intel processor). It won't work if you have a different version.
If you have an Ubuntu 12.04 AMD64, Paradigm4 provides a deployment script and a documentation with very simple steps:
https://github.com/Paradigm4/deployment
Installation from sources
It's not so difficult but it can be painful and time consuming. I did it because we had to compile a custom plugin for SciDB. You have two types of installation: dev install (in SciDB user directory) and cluster install (in /opt/ directory).
You have to be registered on their forum to have the link to the source code. They provide a specific documentation to build from source.
Good luck.
Several months ago I have dealt with porting SciDB 14.12 to an unsupported Linux - Fedora 19. If your OS is not supported, it will neither be supported if you try to install from the sources. You have to start from the sources, but then you have to adapt the deployment and installation scripts. The sources can be downloaded from SciDB forum.
Namely, add a new platform to deployment/common/os_detect.sh. Then, there are multiple platform specific deployment scripts, such as deployment/common/prepare_toolchain.sh, deployment/common/prepare_coordinator.sh and deployment/common/prepare_chroot.sh. You need to make sure those prepare the environment as they would on the supported OS'. I used Red Hat 6 and CentOS 6 as a reference, as those are both more similar to Fedora. Since your OS is Debian, you can first try falling back to Ubuntu deployment (in os_detect.sh).
Another problem you may encounter are the 3rd party tools, specially Boost. In my case, I had to build it manually from sources.
Sometimes when porting and debugging it is not convenient to run the scripts with deploy.sh, but it's better to run the deployment scripts directly on the target machine (e.g. coordinator).
Probably the best way to install and to start with SciDB is to download a standard image. With this image you only have to import the virtual machine with a software to virtualize. Moreover there are some characteristics of this virtual machine that are great to develop your first applications.
The main advantage, is that you have an API to SciDB queries and another to R. Then you can explore all options and to test SciDB.
This is the version that I downloaded few months ago: http://www.paradigm4.com/forum/viewtopic.php?f=14&t=1329&sid=606f614e401900cfa750375ba56de656
Nevertheless, there is a problem, the community is too poor. There are little people developing with SciDB.
I am taking my first steps in the world of iPhone/iPad development with MonoTouch and wish to adopt the practices that I adhere to in my "day" job.
Is there a buildserver for OS X that plays nice with MonoTouch/Nunit?
Thanks kindly,
Dan
Assuming you have MonoDevelop and MonoTouch installed, you can build solutions using the MonoDevelop commandline tool:
/Applications/MonoDevelop.app/Contents/MacOS/mdtool build
For options, run
/Applications/MonoDevelop.app/Contents/MacOS/mdtool build --help
I don't know how you'd get the actual iPhone project to build but of you farm out as much as you can to seperate projects so only the bits that need the funky MT references are in the central UI project you can at least build the rest as normal.
I've just started using TinyIoc which will help in this regard.
As for a specific build server - isnt TeamCity built using Java and Appache? If so there should be no reason why this won't work on your OSX.
That said - why would you want the build server on the same physical machine you dev on?