I have just installed rubymine 5.4.3.2.1 and am trying to start an example project. The problem i am having is that rubymine is asking for a SDK. So where do i point it to?
You should point it to the where you keep your Ruby Binary File, for example:
Windows - d:\dev\Ruby19\bin\ruby.exe
Mac Brew - /usr/local/Cellar/ruby/2.0.0-p247/bin/ruby
Ruby Version Manager - /Users/<user>/.rvm/rubies/ruby-1.9.3-p327/bin/ruby
Linux/Mac Default - /usr/bin/ruby
If you are on Windows and don't have Ruby installed yet, download it from http://rubyinstaller.org/ .
After installing point RubyMine to the ruby.exe file location.
For example, if you install using rubyinstaller-2.0.0-p247.exe into c:\Ruby200 (the default path suggested by the installer), RubyMine would accept c:\Ruby200\bin\ruby.exe path for the SDK (it will even detect it automatically):
Note that it's also recommended to install and configure the DevKit from the same site as it's required for many gems that have native code.
When everything is installed you can follow the Quick Start Guide for RubyMine.
If you are on windows its where ever you installed ruby under the bin folder as diplayed here If you are on a unix base system go to the terminal and enter which ruby and you will point it to the directory listed. Assuming you have ruby installed
Only for Mac, brew, rbenv:
$ which ruby
/usr/local/var/rbenv/shims/ruby
But it doesn't show used gems. So, it's better to add file inside ruby version folder: /usr/local/var/rbenv/versions/*your_version*/bin/ruby
Ruby path in Rails Container: /usr/local/bin/ruby (no RVM installed)
Local Ruby path: ~/.rvm/rubies/ruby-2.6.0/bin/ruby (no default Ruby installed)
Local RVM path: ~/.rvm/bin/rvm
Yes when you add a remote interpreter using rbev, just add the path you get via this command:
which ruby
and it should work fine
If you're sure you have installed the correct Ruby, I've found that invalidating caches and restarting RubyMine can clear this up. You'll find this option on the File menu.
I'm not sure why this works, but it definitely fixed this exact problem for me today.
Related
I am trying to install the typesafe activator (scala, AKKA, play framework, activator)
I have Yosemite OSX
My bash is Oh my ZSH
I already have JDK 1.7, installed and exported
I downloaded and unzipped the file "typesafe-activator-1.2.10-minimal". Finally I put the export path on my ~/.zshrc
but when I type activator on the terminal it prints that cant find the file
thank you
get HomeBrew.
play documentation says this :
Play install on mac
But there have been some changes to that. Now you have to do this.
Try this:
brew install typesafe-activator
And then use activator command to start it
I made a big mistake, In the ~/.zshrc where I should put
export PATH=$PATH:/relativePath/to/activator
I added the executable file to the path. I post this answer in case is helpful for someone else.
For people like me, who are reading this in 2019 (or later) and are unable to find activator recipee in homebrew, be informed that activator has been decommissioned
Good news is, it's fairly simple to create new projects (including templates for play, akka etc.) with sbt new command and Giter8 templates.
Open terminal and follow the below steps,
mkdir ~/bin
ln -s <path to your play home>/activator ~/bin
echo "export PATH=~/bin:$PATH" >> ~/.bashrc
. ~/.bashrc
These days, in 2020, it seems Activator isn't available from Homebrew anymore?
But old Activator releases remain downloadable, from e.g. https://downloads.typesafe.com/typesafe-activator/1.3.6/typesafe-activator-1.3.6.zip. (I assume other version numbers work as well.)
export PATH=$PATH:/Users/XXX/XXX/activator-dist-1.3.12/bin
At first I downloaded Less from GitHub and saved the folder on my disk. After that, I tried to locate the compiler (file lessc) in my Netbeans IDE (7.4 Beta). After that, I got the following Error-Message:
I'm not sure if Less compiler can work without NodeJS. So I would do following:
install NodeJS (nodejs.org)
install less compiler using npm
npm install -g less
then NetBeans should find it, if not, you need to specify path to lessc.cmd, e.g.
C:\Users\lada\AppData\Roaming\npm\lessc.cmd
to find where is your lessc.cmd, run following in command line
where lessc.cmd
The lessc (without cmd) is for Linux and Mac OSX
I downloaded lessc from here:
https://github.com/duncansmart/less.js-windows
unzipped the zip-file and copied all files to C:\bin\lessc but you can copy it anywhere you like.
Then just point Netbeans to that folder and lessc.cmd and it should work.
Try:
Install nodejs
Install less in nodejs "cmd: npm install less"
less path netbeans: C:\nodejs\node_modules.bin\lessc.cmd
The instructions how to install GoClipse have been followed.
I'm not getting any autocomplete stuff happening at all, either for local packages that I write, for built in stuff, or for GAE stuff (I have downloaded Go src to the SDK folder as the wiki states).
Are there any settings that I can check to ensure it is set up correctly? Is autocomplete supposed to work in the current version?
As the GoClipse with AppEngine article you linked to says:
We assume the reader has a working copy of GoClipse running in their Eclipse environment.
so that’s not the article you want to refer to. Instead, check for GoClipse.
The auto completion is named content assist in eclipse. The GoClipse features state:
Now delivered with content assist via Gocode for Windows, OS X 64bit, and Linux 64bit.
Gocode is an auto-completion daemon. So you will also have to install and run that one besides your eclipse + GoClipse.
There is a bug in the current version of Goclipse for the Linux platform. It currently delivers a prebuilt version of gocode for Windows, 64 bit OS X, and 64 bit Linux. I have only been able to test it locally with limited resources, so I really depend on users to report the problems they find at:
http://code.google.com/p/goclipse/issues/list
If you are having problems, I urge you to download and install gocode into your $GOROOT/bin directory and see if that helps. Otherwise, the fix will come in the next release in a few days.
Also, sorry for causing you any trouble and thank you for trying Goclipse.
If you are not using a gocode upstream (but the one shipped with Eclipse) on Linux you are also no be able to build your application with CRTL+F11, although just clicking in Run->Run is going to work.
So, I strongly recommend to update your gocode on Linux, as simple as:
$ sudo GOPATH=/opt/go/ go get -u github.com/nsf/gocode
I have installed Eclipse 3.5.2 and the plugin Subversion JavaHL Native Library Adapter 1.6.9.2 and this worked without any problems. However, this morning I was forced to change the password to logon to my Mac and since then I get the message that "Subversion native library not available" when I try to save any changes. Can anyone help? I have tried to add this line (-Djava.library.path=/usr/lib/jni) to the eclipse.ini file but this didn´t seem to make any difference.
Can anyone help?
Install MacPorts or HomeBrew, then run the following command:
For MacPorts, the commands to run are:
sudo port install subversion-javahlbindings +no_bdb +universal
For HomeBrew, the command is:
brew install --universal --java subversion
I was having a similar problem on Mac OS X Snow Leopard. I suspect your libraries are there but just need permissions changed, whereas I didn't have the libs at all.
The directory to check is /opt/subversion/lib, see if it has any libsvnjavahl files. In your case they may be there and just need new permissions.
To get the files I followed the the instructions they give for installing JavaHL on OS X, which is to download and install Open CollabNet. (login required, although it's free)
Then you just need to update your environment variable in .profile, something like:
export PATH=.:/opt/subversion/bin:$HOME/bin:$PATH
Then ran:
. .profile
Then I tested with javahltests.jar as mentioned here.
The easiest thing to do is download and install the OSX package that is provided on openCollabNet.
MacPorts also provides an easy Subversion and JavaHL package, however on Snow Leopard ?MacPorts is still compiling these packages as simple 32-bit binaries. If you use the default Snow Leopard JVM which is 64-bit you will get an error...
Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
no svnjavahl-1 in java.library.path
/opt/local/lib/libsvnjavahl-1.0.0.0.dylib: no suitable image found. Did find: /opt/local/lib/libsvnjavahl-1.0.0.0.dylib: mach-o, but wrong architecture
Note the error about wrong architecture. This is because the 64-bit JVM cannot load a 32-bit native library. The ?CollabNet binaries for OSX do not have this problem because they include both 32-bit and 64-bit versions.
Source: subclipse.tigris.org
Here is a blog entry that gives a solution:
http://blog.mattwoodward.com/getting-rid-of-subversion-native-library-not
I don't know whether this will work in your particular situation, but it's worth a try.
(Edited to fix link that became broken after I posted. The link became broken sometime between May 3 and June 1.)
In case you already have subversion installed I'd recommend performing first a brew uninstall and then the install again. And follow the steps to create the links indicated after the install concludes. This worked for me. Regards
I fixed it installing the SVNKit Client Adapter (not required) package.
How can I get PDO to work on my mac (os x 10.5)? I'm using the built in php and php in Zend/Eclipse. Can't seem to find useful drivers for it at all.
I had to install the PDO_PGSQL driver recently on Leopard, and I ran across a multitude of problems. In my search for answers, I stumbled across this question. Now I have it successfully installed, and so, even though this question is quite old, I hope that what I've found can help others (like myself) who will undoubtedly run into similar problems.
The first thing you'll need to do is install PEAR, if you haven't done so already, since it doesn't come installed on Leopard by default.
Once you do that, use the PECL installer to download the PDO_PGSQL package:
$ pecl download pdo_pgsql
$ tar xzf PDO_PGSQL-1.0.2.tgz
(Note: you may have to run pecl as the superuser, i.e. sudo pecl.)
After that, since the PECL installer can't install the extension directly, you'll need to build and install it yourself:
$ cd PDO_PGSQL-1.0.2
$ phpize
$ ./configure --with-pdo-pgsql=/path/to/your/PostgreSQL/installation
$ make && sudo make install
If all goes well, you should have a file called "pdo_pgsql.so" sitting in a directory that should look something like "/usr/lib/php/extensions/no-debug-non-zts-20060613/" (the PECL installation should have outputted the directory it installed the extension to).
To finalize the installation, you'll need to edit your php.ini file. Find the section labeled "Dynamic Extensions", and underneath the list of (probably commented out) extensions, add this line:
extension=pdo_pgsql.so
Now, assuming this is the first time you've installed PHP extensions, there are two additional steps you need to take in order to get this working. First, in php.ini, find the extension_dir directive (under "Paths and Directories"), and change it to the directory that the pdo_pgsql.so file was installed in. For example, my extension_dir directive looks like:
extension_dir = "/usr/lib/php/extensions/no-debug-non-zts-20060613"
The second step, if you're on a 64-bit Intel Mac, involves making Apache run in 32-bit mode. (If there's a better strategy, I'd like to know, but for now, this is the best I could find.) In order to do this, edit the property list file located at /System/Library/LaunchDaemons/org.apache.httpd.plist. Find these two lines:
<key>ProgramArguments</key>
<array>
Under them, add these three lines:
<string>arch</string>
<string>-arch</string>
<string>i386</string>
Now, just restart Apache, and PDO_PGSQL will be up and running.
Take a look at this PECL package: PDO_PGSQL
I haven't tried it myself, but I've been interested in playing with Postgres as an alternative to MySQL. If I have a chance to try it soon, I'll throw my results up here in case it helps.
I'm not sure this will help with the PDO drivers specifically, but you might look into BitNami's MAPPStack.
I had a ton of trouble with Postgres, PHP, and Apache on my Mac, some of it having to do with 64- vs 32-bit versions of some or all of them. So far, the BitNami MAPPStack install is working nicely in general. Maybe it will help with your PDO issues as well.
Install new php version via brew and restart server, and php -v, all issues are removed.
This is what worked for me
brew install php55-pdo-pgsql
This installs PHP 5.5.32 and PostgreSQL 9.5. I already had PostgreSQL 9.4 installed so I uninstalled the homebrew version with:
brew uninstall postgres
You then have to update /etc/apache2/httpd.conf to point to the correct PHP version and restart Apache:
LoadModule php5_module /usr/local/Cellar/php55/5.5.32/libexec/apache2/libphp5.so
My OSX version is Yosemite.