This question already has answers here:
How to use sbt from behind proxy?
(16 answers)
Closed 8 years ago.
I am trying to run sbt behind a firewall, and there is no way I can disable it. But somehow I can get the required jars and store them on the system. Is there a way I can run sbt without internet connection on that system.
I am using Windows (Win7) as the development environment.
SBT has an offline mode, from a command line you can use:
sbt "set offline := true" run (replacing run with whatever command you need)
or if you ran sbt and are in a sbt console you can simply do set offline := true
I finally found the answer to the question after struggling for two days. The problem was not with the firewall but with the proxy set up. What I had to do was pass the proxy, username and password via command prompt so that it could get the necessary jars.
java -Dhttp.proxyHost=proxy -Dhttp.proxyPort=8080 -Dhttp.proxyUser=proxyUsername -Dhttp.proxyPassword=proxyPassword -cp "/sbt-launch.jar" xsbt.boot.Boot
I ran this piece of code and it solved my problem.
The jars that are downloaded are stored in the .ivy/cache/ path.
Thank you #Exupery for your help.
Related
I want to use Python3.6 in windows sandbox, I installed the same in my windows host machine at
C:\Users\Local_Admin\AppData\Local\Programs\Python\Python36\
I tried passing python to sandbox through configuration file as mapped folder but no luck.
<HostFolder>C:\Users\Local_Admin\AppData\Local\Programs\Python\Python36\</HostFolder>
<SandboxFolder>C:\Users\Local_Admin\AppData\Local\Programs\Python\Python36\</SandboxFolder>
I can use python36 in host machine as I set environment variable but not in sandbox, can anyone suggest why else need to be done?
To make things easier on you, I would suggest you try using Virtualenv. It allows you to create a Sandbox environment so you can run python code without breaking anything. It has documentation and is easy to setup. I have used it in the past for windows.
I've been trying to build a CordApp and I downloaded the template from GitHub. The code that I've written is available on the following link:
https://github.com/shanmukhipriya99/taskcordapp
When I'm trying to run gradlew.bat deployNodes in the cmd terminal, this is what I got:
[gradlew.bat deployNodes]
Then when I run build\nodes\runnodes in the cmd terminal, this is what I got:
[build\nodes\runnodes]
Then I have three other terminal windows opening-up, they load the Corda part, show some red text that says something about the developer mode and all the node terminals get closed automatically before I'm able to read the entire text.
Can someone please help me in figuring out where I'm wrong!?
Thanks in advance!
It looks like you have had successfully started the nodes all in one terminal. I am not entirely sure, if this is the only issue, but I have seen this issue before. This is caused by lack of permission of the Terminal.
I have seen it happened for both Windows and Unix/Macos users. To resolve it you might need to grant the permission to Terminal manually.
If it still does not work out, I would actually suggest the alternative quick fix that Ashutosh mentioned in comment. Open a new tab and go to the root folder of each nodecd /build/nodes/XXX, and start the node manually via java -jar corda.jar
I'm having problem with the infamous:
"/Users/n/Library/Developer/Xcode/DerivedData/Build/Intermediates/XCBuildData/build.db":
database is locked Possibly there are two concurrent builds running in
the same filesystem location
How do I fix broken "modern" build system getting stuck with a locked database?
I tried:
Cleaning the project
Deleting derived data
Updating cocoapods (sudo gem...) and pod install
Full nuking of Xcode folder with a fresh reinstall from App Store
Now I'm with a fresh Xcode installation, the project worked for a dozen builds(real device and simulator) and the problem comes back, making me unable to work on a project. How I can reset the locks on build.db or delete it?
I see this question asked multiple times, and the answers do not solve my problem. I'm not using build scripts, all I have is a couple cocoapods. Please do not close this question, as I'm asking specifically about lack of:
NO CUSTOM SCRIPTS
NO CONSOLE BUILDS
NO COMPOSITE TARGETS
The only thing that lets me continue working is turning to the legacy build system:
How can I use the legacy build system with Xcode 10's `xcodebuild`?
Xcode 10: unable to attach DB error
I encountered this when tinkering with cli, swift run democli. The error I got was:
unable to attach DB: error: accessing build database "/Users/xman/Desktop/democli/.build/x86_64-apple-macosx/build.db": database is locked Possibly there are two concurrent builds running in the same filesystem location.
I just remove the build.db, and the DB error is gone.
So far the only way to fix this is to turn the "Legacy Build system" on in File > Workspace settings. After certain number of computer restarts (or time elapsed?) the setting can be changed to the "new" build system again and it will build.
I managed to compile my project by adding to the xcodebuild command line:
OBJROOT="${OBJROOT}/DependentBuilds"
Thanks to this post: https://github.com/mattgallagher/CwlSignal/issues/24#issuecomment-396931001
I encountered the same issue while using Fastlane and the New Build System.
After switching from xcodebuild( ) to build_app( ), the issue was resolved.
The legacy build solution is too temporary. You can only use that from within XCode. You can't use it within VSCode, so you lose the Hot Reload sweetness.
I want to use gitLab-CI for a Qt-project, but i can't figure out, what I need to do so. I understand, that the whole pipeline process takes place on the CI-Server, but how do I setup the needed requirements like the qt-environment?
Solution:
Ok now I got it! You just use the Runner for it, if you do not have a Server, you can use a VM.
For GitLab.com
The runners are already set up (shared runners).
You need to use a Qt SDK Docker image or install it yourself:
Use image: <image-name> for .gitlab-ci.yml
Use apt or some other package manager (not recommended)
Once you got a Qt SDK environment set up inside .gitlab-ci.yml, make sure to add a command to build/compile/run/test it.
For non-GitLab.com
The runners may or may not be set up, but you do not need to do any specific changes (other than using faster machines with bigger memory, etc for building in necessary).
You need to use a Qt SDK Docker image or install it yourself:
Use image: <image-name> for .gitlab-ci.yml
Use apt or some other package manager (not recommended)
Once you got a Qt SDK environment set up inside .gitlab-ci.yml, make sure to add a command to build/compile/run/test it.
Other Helpful Comments
This is from Josh Peak's comment:
Ok that answers my question. I'm going to have to preconfigure a VM image and/or a Docker image with the QT SDK that the rest of my dev team can leverage. Thanks for the quick response.
This answer is from ManuelP.'s question:
Ok now I got it! You just use the Runner for it, if you do not have a Server, you can use a VM.
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
How to compile and run xv6 on windows?
We are being taught xv6 in our course. Currently we use to login to linux server of our school using putty in windows.
There we make changes in source of xv6 (using vim), then compile and run it in qemu simply
make clean
make
make qemu-nox
It is not always possible to connect to their servers therefore I want to be able to compile and run xv6 withing windows (in some emulator obviously).
What emulator I can use for above kind work? (edit code, compile and run) and how?
You should be able to build the xv6 system using cygwin from www.cygwin.org; make sure you install gcc, make and a decent editor (emacs or vim or just use a regular windows editor like notepad++). After that, you can run the resulting image with one of the qemu ports for windows; I found Qemu Manager to be quite easy to use (http://www.davereyn.co.uk/download.htm). You will have to modify the Makefile to point to the proper qemu location.