We are trying to build https://github.com/wso2/emm-agent-ios app using XCode 6.3.2.
In order to avoid issues with libOHTTPStubs library I have changed the following projects settings:
Architectures: i386
Build active architecture only: NO
Then I prepared an app ID on Apple Developer portal, configured Push notifications using the same CertificateSigningRequest as I prepared following your instructions at https://docs.wso2.com/display/EMM110/iOS+Client+Configurations
I also prepared an Enterprise In House Provisioning profile and successfully archived the app.
Problem is I can’t export it for In House or anything else, Xcode says “The archive contains nothing that can be signed”
Your architectures have to include arm64, since i386 is only for the simulator. If you can build and run the code on an iPhone or iPad you should be able to export it.
Related
I am currently in the process of migrating a couple of legacy Qt5 projects to a new Team Foundation Server. All projects have been developed for Windows in Visual Studio using the Qt VS AddIn (and thus don't use .pro-files). I would love to use the TFS Build Agent to build these on other platforms (mainly linux).
I have previously done this on other projects using Jenkins and qmake, having platform-dependent settings in the .pro-file.
Is there an established workflow for building VS projects using Qt5 via a TFS Build Server on other platforms?
I don't use TFS but, since TFS Build operates on Visual Studio solutions, it ought to be possible to use the "Linux development with C++" feature of VS2017. Just setup a Linux project in the VS solution and it should build like any other.
Seems you'd like to build Cross-Platform Code in Linux using TFS vNext build system. To build or deploy you'll need at least one agent. The cross platform build agent is support on Ubuntu, Red Hat, and CentOS.
Detail steps please refer this tutorial-- Deploy an agent on Linux. Then simply create the build definition add build task, select the Linux build agent the same as build on windows. More detail step and build configuration you could take a look at this video tutorial-- Building and Deploy Applications In Linux With TFS
In your case, there is not corresponding VS/Qt VS AddIn in your Linux environment. You need to set up your Linux build agent local environment to build your qt5 application successfully, then it's not hard to build through tfs.
Another way is scripting the Linux build process to run over SSH or some other remote protocol, and driving this process from the Windows build agent.
I've managed to set WSO2 EMM 2.2.0 server and have tested out the emm android agent which works. However, for "Android for work", when I tried to push enterprise applications, it says that "Your administrator doesn't allow installation of apps obtained from unknown sources".
Is there a way to install the apps in the work profile from unknown sources?
The intention of work-profile is to have a safe container for work-related data. Therefore Android is not allowing to install apps from unknown sources in work-profile what so ever. What is only possible is enabling playstore in the work-profile and downloading apps from there.
The only work-around that you can do to install apps from unknown source is by ADB.
Configure the work profile first and then using ADB push an app to the device. The app will be installed in both work-profile and personal profile.
At the moment that is the only work-around possible.
Android for Work is still not saturated. There are grey areas to be addressed. I believe Android will come up with options for this scenario soon.
I am experimenting with setting up Visual Studio Code as my Django IDE, however I'm having difficulty configuring my python workspace environment correctly, such that I can get intellisense for 3rd party modules (like Django) working.
My desktop is Mac OSX, but I run my actual Django environment in a Debian instance inside of virtual box, running on my Mac. I also run Debian in production. I use an NFS share my django project files and virtualenv files between Debian and OSX.
I tried following these instructions for configuring my interpreter, however if I set a custom path like:
/Users/myusername/.virtualenv/myenv/bin/python2.7
It won't work, because that's a debian binaries, not Mac OSX.
In PyCharm I believe there is a way to specify remote interpreters, even on different architectures. There's no way to do something like this in VS Code, right?
Pretty sure what I want is currently impossible. The good news is it's being worked on.
link to issue #123 RFE: Support Remote Interpreter in pythonVSCode repo
I used to use Anvil (through hammer) to build some native libs to be bundled with a rails app. Specifically I was building libapngasm using this:
https://github.com/Kagetsuki/heroku-buildpack-apngasm
Unfortunately it seems Anvil has been discontinued and I couldn't find any information on how to do a remote build and retrieve the resulting binaries through the Build API.
Is there a new alternative to Anvil? What is a "correct" way to do this?
OK, the official answer here was a little more obvious than I had expected. Basically if you're running the same gcc/libc~ as that stack your dyno is running compile locally. Otherwise just spin up a VM or a docker image with a compatible version and build on that. Then just vendorize the libraries/binaries into your app repository so they'll be bundled up with the slug when you push. Finally, set your heroku environment load path to find the libs/bins you bundled.
I want to build an application that will be compatible with, say, Debian Lenny (libc, postgres, oracle and other libs) on a different Debian/Ubuntu release.
Is this possible? If so, where can I read how to do it?
You can use the open build service for this. Create the Debian package description files for it (you can add also rpm spec files), select the target distributions and you will get it built on each platform and also get a specific download repository for each platform. Your package will be rebuilt automatically when needed as well. You can install your own instance of the service if you need to host proprietary code.
If you want a multiplatform binary, you may want to build it against a LSB chroot:
http://ftp.linux-foundation.org/pub/lsb/impl
And bundle any library that is not part of it. The LSB has tools to then check your app for compliance. Their website is down right now, but it should be here: http://ldn.linuxfoundation.org/lsb/check-your-app