I am trying to run some code on RPi2 and unfortunately I am forced (thanks to haxeui) to use legacy version of the lime. There is no precompiled version for RPI, so I have to build it on my own.
Trying to run hxcpp build in on legacy/project ends up with error, that options file is not provided.
Second thing I tried is executing
lime rebuild linux -Dlegacy -Drpi -v
But it seems, that legacy flag get overridden with the rpi as no legacy file is created.
I am using git version of lime/openfl/haxe/hxcpp on latest rasbpian which I compiled thanks to the http://www.gepatto.nl/get-piratepig-running-on-a-raspberry-pi-2-with-raspbian-jessie/ tutorial.
How can I run build with both legacy and rpi flags?
thanks
Via OpenFL forum, current dev branches does no longer support legacy, yo you need to switch to openfl3 branch for openfl and master branch for lime.
Related
I'm trying to run the Kotlin/Native Hello Program
but the terminal says the command kotlin-native cannot be found. I'm on a MacBook, using zsh (get same error when I use bash) and installed Kotlin via Homebrew before, so kotlin and it's compiler works on my machine, the kotlinc command works just fine. I'm trying to use the compiler instead of gradle for now. Is there a different command I'm supposed to be using?
It sound like you may have had a similar problem to me. Installing kotlin-native via homebrew did not install the kotlinc-native command.
To get the command working, I had to do the following:
Go to https://github.com/JetBrains/kotlin/releases and get the latest version of Kotlin
Extract it to .kotlin in the home directory
Add export PATH="$HOME/.kotlin/bin:$PATH" to .zshrc
The problem with this method is that it's completely disconnected from Homebrew. You will have to run the steps again every time you want to update Kotlin.
You've typed kotlin-native but the tutorial says kotlinc-native, which is the actual name of the process file.
If kotlinc works then you might just have a typeo.
I don't use these processes directly, but I'm somewhat familiar with them. My guess is check the name.
Summary: The pkg-bootstrap.jar and related files are missing from the latest GlassFish 4.1.2 and this prevents the updatetool from running. What is the proper way to install and run updatetool on Windows 10?
Detail: I was working with the Java EE 7 tutorial and downloaded the Java EE 7 SDK Update 3 (not Web Profile) which is based on GlassFish Open Source Edition 4.1.2. I ran into a problem running the updatetool on Windows 10. When run, it gives the option to install itself but the installation fails. It looks like the update tool uses the pkg tool, and that uses a pkg-bootstrap to install itself the first time. However, this is no longer included in GlassFish 4.1.2. When the updatetool is run, it produces the following errors:
C:\glassfish4\bin>updatetool
The software needed for this command (updatetool) is not installed.
If you choose to install Update Tool, your system will be automatically
configured to periodically check for software updates. If you would like
to configure the tool to not check for updates, you can override the
default behavior via the tool's Preferences facility.
When this tool interacts with package repositories, some system information
such as your system's IP address and operating system type and version
is sent to the repository server. For more information please see:
http://wikis.oracle.com/display/updatecenter/UsageMetricsUC2
Once installation is complete you may re-run this command.
Would you like to install Update Tool now (y/n): y
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar" refresh
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar" "C:\Users\[userid]\AppData\Local\Temp\pkg-bootstrap21687.props"
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar
C:\glassfish4\bin\pkg does not exist in either the latest Java EE 7 SDK Update 3 or the latest GlassFish 4.1.2. Some research on the nightly builds shows that the directory trees glassfish4/.org.opensolaris,pkg and glassfish4/pkg were removed between builds glassfish-4.1.2-b03-02_25_2017 and glassfish-4.1.2-b03-03_07_2017. I can't find anything that explains why they were removed or an alternate way to install the updatetool. My work around was to copy the two trees from glassfish-4.1.2-b03-02_25_2017 into c:\glassfish4 (from the Java EE 7 SDK Update 3) and that seems to work. But, I figure that if this was removed, there was a good reason for it, and I shouldn't be hacking it.
If there was a separate installation step for the package tool, I missed it. What is the proper way to get the updatetool to run on GlassFish 4.1.2?
I have jdk1.8.0_121 and jre1.8.0_121.
Thanks for your help.
I had the same problem as DevDevDev.
I went to the link in his post:
http://download.oracle.com/glassfish/4.1.2/nightly/index.html
Downloaded the archive:
glassfish-4.1.2-b03-02_25_2017
http://download.oracle.com/glassfish/4.1.2/nightly/glassfish-4.1.2-b03-02_25_2017.zip
Extracted the missing folders into my glassfish directory:
/glassfish4/pkg
/glassfish4/.org.opensolaris,pkg
As DevDevDev I have questions about why it was removed but it works for me...for now.... Hope it helps someone else. Thank you DevDevDev I would not have solved this without your post!
I was working with Java SE. Then I needed to work with JAX-WS, so I went into the same website as you.
Basically, it says that you have to:
Download the package (a compressed file with a folder called glassfish4)
Unzip the downloaded file (does not specify where)
voilá
It did not work for me, so I kept searching and I found this: https://forums.netbeans.org/post-91328.html
You just need to download this update from netbeans plugin Manager:
"Java EE Base"
Good luck!
I got the same problem too. It seems that glassfish 4.1 did not integrate the Update Tool, so as doc of oracle suggests, we'd better install SDK 6(glassfish 3). Here is Java EE 6 SDK Update 3, note that the version provided here is with JDK 7. If you already installed JDK in your windows 10, you may ignore it.
When you finish downloading the .exe file, you should not install SDK by double-click the .exe file. Instead, you should run below command:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j [JRE-Home]
note, command here is the name of your .exe file and it needs console arg of JRE Home, mine command is as below:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j D:\JDK\jre
It seems that unzipping the file using Windows explorer's zip support doesn't work properly. If you instead do as described in the README and run:
jar xvf glassfish-4.1.zip
The archive is extracted properly and all the needed pkg files are there.
What files do you need? I had the save problem I was looking for the files of tutorial. Finally I found them here: ..../glassfish4/docs/javaee-tutorial/
I just install the latest netbeans 7.4 RC1 , i got the Error page "Netbeans Cannot Find Cordova or Git on your path, Please install Cordova or Git". In fact, i actually did install both cordova and Git.
I Do follow the step on this youtube ,
https://www.youtube.com/watch?v=Gt4uHSiO-00
but it is still not allow me to open any HTML 5 cordova project.
Is that any steps i left out ?
I had the exact same problem. I found this bug: https://netbeans.org/bugzilla/show_bug.cgi?id=234870
Go to the command prompt.
Try typing:
git --version
cordova --version
If you get a "command not found" error, you have an issue with your installation. More than likely you need the items added to your path variable.
In my case, that was
C:\Users\Chris\AppData\Local\GitHub\PortableGit_015aa71ef18c047ce8509ffb2f9e4bb0e3e73f13\bin;C:\Users\Chris\AppData\Roaming\npm
for both Cordova and Git.
I think the error message logic is broken, that's why this is misleading. In my case, git wasn't in the PATH, but cordova was. Making sure git was added to the PATH, fixed this.
Had the same exact problem, looking here https://netbeans.org/bugzilla/show_bug.cgi?id=234870 this answer solved my problem:
On Windows, NetBeans tries to run "cordova.cmd -v" to check if Cordova
is ready. So I modified this cordova.cmd file to simply return fake
version:
#echo 3.0.1
this allows me to get through the wizard step, where is being checked
if Cordova is installed. After that, I revert changes in cordova.cmd
and finished new project wizard. And it worked and I can even build
and start it on Android device. This "workaround" works until I close
IDE. So the problem is only at the beginning in checking if Cordova is
installed
On command line run
where cordova
to get where it is located (usually in C:\Users\\AppData\Roaming\npm)
You have to use cordova version 3.0.10 instead of 3.1
Netbeans does not seem to work with Cordova 3.1
type in
npm install -g cordova#3.0.10
and restart Netbeans.
Be sure to check if you have any enclosures in your environment variables. I made this mistake and it gave me a lot of headache :)
Not okay: "C:\Program Files\nodejs\";C:\Program Files (x86)\Git\bin
Okay: C:\Program Files\nodejs\;C:\Program Files (x86)\Git\bin
If you install Netbeans 8 on Ubuntu 14.04, you should type
sudo ln -s /usr/bin/nodejs /usr/bin/node
then follow http://cordova.apache.org/docs/en/edge/guide_cli_index.md.html#The%20Command-line%20Interface
I had the almost the same problem using NetBeans 8.1 on Windows 7. Except NetBeans said Cordova (only) cannot be found on my PATH but Cordova was installed and on the PATH. So like everyone suggested, I tested the versions.
C:\>git --version
git version 2.7.0.windows.2
C:\>cordova --version
? May Cordova anonymously report usage statistics to improve the tool over time? No
You have been opted out of telemetry. To change this, run: cordova telemetry on.
6.2.0
Strange, the --version asked for user input which I gave. I reopened Netbeans to find it can now magically see the install of cordova. Come to find out my whole problem was that Netbeans couldn't see it installed because Cordova was forcing user input the first time cordova --version was ran. Cordova had been freshly installed and never ran.
If anyone is using Netbeans 8.0, this is the tutorial you need to follow provided on the website of Netbeans: https://netbeans.org/kb/docs/webclient/cordova-gettingstarted.html
Happy coding with cordova...!!!
I solved this problem with installing GIT from this link :
http://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup
hope this help someone.
I had the same problem. I found the one solution on another site.
Try this: re-install git and choose the option *Use Git and optional Unix tools from the windows Command Prompt.
Just follow the installation process as describe in phonegap(cordova) documentation but make sure when you are installing git you checked the option use git and optional Unix tools from the windows command prompt after that go to path variable check that C:\Program Files\nodejs\;C:\Program Files
(x86)\Git\bin exists in your path environment variable as shrty has said.
You can test if node.js is install by node --version and git by git --version
Get the path where npm install -g cordova installed your
cordova. It produces something like "} (current: {"node":"0.10.36","npm":"1.4.28"})
C:\Users\kanu\AppData\Roaming\npm\cordova ->: if you go in
C:\Users\kanu\AppData\Roaming\npm\ directory you'll find cordova.exe there
What you have to do is to add ;C:\Users\magezi\AppData\Roaming\npm\ in environment after the git's one.
After that change the directory to where cordova.exe exists for me it was in C:\Users\kanu\AppData\Roaming\npm\ and from there you can test the installation of cordova by the command cordova --version(it will return the version)
open netbeans and try to create an cordova application. It should work
I had the same issue under linux, and was tinkering around with the user specific $PATH. What solved it eventually was to set the $PATH variable in the netbeans.conf located at $NETBEANS_PATH/etc/netbeans.conf
I added these three lines
export ANDROID_HOME=/home/paul/Android/Sdk
PATH="$PATH:/home/paul/opt/node-v4.4.7-linux-x64/bin/:/home/paul/Android/Sdk/tools"
export PATH
Afterwards I was finally able to setup any Cordova project :)
First, I obviously tried to get a binary release of Mono.Fuse project, but the only available downloads were the source files. (And actually it seems that latest release has a syntax error in an override)
So I tried to install it on a Linux box from git, successfully, but I'll soon need to bring it to a production server together with my Xcopy-deployable application.
I don't like compiling software on a production machine, especially because I need to install loooooooooooots of development tools from YaST. So now I have this git-cloned directory with all source and compiled files.
How can I create an RPM package that I can install on multiple production machines with a simple command without resolving configure.sh's dependencies with lots of unneeded libraries like glib-2.0-devel?
Take a look at Open Build Service.
I'd very much appreciate anyone sharing best-practices, patterns, anti-patterns, backup, rollback processes that you have formulated for a pain-free, foolproof, Play framework upgrade.
I'm thinking just replacing the bin/play directory with the latest version can cause problems
Edit:
I'm looking for more specific version management strategies, say,
a) Do you just have /bin/play directory having the latest play version or
b) Do you keep versions like /bin/play-1.1 /bin/play-1.2 and change your $PATH to point to the latest (cons: you have to rebuild your modules, dependencies & libs; pros: gives better control over rollback)
I prefer to install play from source using git:
git clone git://github.com/playframework/play.git
cd play
# checkout specific version
git checkout 1.2.1
cd framework
ant
cd ..
ln -s $PWD/play ~/bin
So I have a full install including all source. Later, when play was updated to version 1.2.2 I did the following:
cd <play_home>
git pull
git checkout 1.2.2
cd framework
ant
In your application you then do
play clean && play run
The advantage of running play from a source build is that you can always and easily roll back to the previous version or even test out features from current development. This does not solve the problem of having multiple versions of play active at the same time though.
I agree with Andre. However, if you are asking for best practice for a live project, I would do it differently.
You can have multiple version installed on your local machine. The only thing you have to change is which one is visible in the path. For instance you could have 1.1, 1.2, 2.0 and depending on which one you want, you just modify your /home/youruser/.bashrc file.
The reason, why simple update of play from git or hg will not work/good idea is because, incase there are problems, you have to revert, rollback modules, or goodness know what not.
It is far better to simple swap out the play version, rebuild, test extensively, once you are ok that everything is good, then you can make the same changes in a live site.
If things don't workout, or your are hopelessly lost, all you have to do is revert the changes to your project and switch the play version. You will be back to where you started.