When you do gem install someGem, does it install it in your system so it's available for all your projects, or does it only install it for the project that's associated with the folder you're currently in?
This depends on how it is set up. Normally it would be available for all projects but it can be set up as in this tutorial http://janveldeman.wordpress.com/2008/04/14/project-specific-rubygems/ (From 2008 so might require a big of playing to get working with newer versions) to be specific to individual projects.
Related
I've seen this post and this other one. The list goes on.
However, I need to install MinGW (preferably the latest version) in a Windows machine which is purposefully isolated from the internet. The purpose is to use soem features of Matlab 2018b that require a compiler. I can upload files to it within some restrictions, but I can neither use the default MinGW installer, nor can I use the "Get Add-On" menu command.
By the way, the machine works with windows server.
How can I get an installer or a set of files that would allow me to install MinGW?
For versions 2016b and newer, MathWorks provides a tool that allows downloading support packages and sending them to off-line environments. The tool can be downloaded here and will require admin permission to install. With it, you can select packages to download at a target folder, and later transfer them to the off-line environment.
For each package there will be a readme file with the relevant instructions.
I just install meteor.js and try to use it replace the old frameworks.
The issue is:
On my windows 10 64bit system, the meteor is use 32bit mongodb(2.6.7), which is limited th database size is 2gb.
How to make the meteor work with 64bit mongodb?
Having researched this myself just now, it looks as though the Meteor version 1.4 release will be updated to version 3.2 of MongoDB, in which "32-bit binaries are deprecated"
Github ticket for the updating of MongoDB
MongoDB declaration that 3.2 has deprecated 32-bit binaries
Meteor 1.4 announcement
If upgrading your MongoDB instance is mandatory now, then unfortunately it looks like the only way is to manually upgrade the binaries yourself. If you do this, I would suggest you make a backup of them just in-case it messes up.
To upgrade to version 3.2 you first need to upgrade to version 3.0, then you can upgrade to version 3.2
I guess you didn't install the right version of Mongo if you have a 32 bits version.
check out their installation guide:
https://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/
First download the right 64 bits version for Windows:
https://www.mongodb.org/downloads#production
and follow the instructions:
Install MongoDB
Interactive Installation 1 Install MongoDB for Windows. In Windows
Explorer, locate the downloaded MongoDB .msi file, which typically is
located in the default Downloads folder. Double-click the .msi file. A
set of screens will appear to guide you through the installation
process.
You may specify an installation directory if you choose the “Custom”
installation option.
NOTE These instructions assume that you have installed MongoDB to
C:\mongodb. MongoDB is self-contained and does not have any other
system dependencies. You can run MongoDB from any folder you choose.
You may install MongoDB in any folder (e.g. D:\test\mongodb).
First, a little background info:
Versions 1.x of my Windows software connect to hardware platform A, and the software is installed using a .msi install script (created with VS2010 and a .vdproj file).
Versions 2.x of my Windows software are similar to versions 1.x, but the v2.x software only connects to hardware platform B (second-generation hardware). This software is installed using an updated version of the same .vdproj file, build with VS2013.
The above is all well and good, but the problem is that since v2.x of the software controls different hardware than v1.x, users who own both platform A devices and platform B devices will want to have both v1 and v2 of the software installed simultaneously, and the .msi files currently don't allow that.
Specifically, trying to install v2.x while v1.x is installed auto-removes the v1.x software, and trying to install v1.x while v2.x is already installed results in an installation abort, with an error dialog saying "a newer version of the software is already installed".
What I'd like to do is disassociate the 2.x versions of my software entirely from the old v1.x versions, so that (as far as the installer's logic is concerned) they are completely unrelated projects. They already install to different default install paths (e.g. "\Program Files (x86)\MyCompany\MySoftware v1" vs "\Program Files (x86)\MyCompany\MySoftware v2"), so that shouldn't be a problem, its just that something in the .vdproj file is still keeping the two projects associated with each other.
I tried changing the "UpgradeCode", "PackageCode", and "ProductCode" GUIDs in the v2.x .vdproj file to something different, but that didn't seem to help; installing v2.x of my software still results in the auto-uninstall/deletion of the v1.x install, and the v1.x installer still aborts if v2.x is installed.
Can someone who is more familiar with the .msi installer's behavior give me a hint on how to make it a little less clever?
For the record, I figured out the problem.
Changing the UpgradeCode value is all that is necessary to achieve the behavior I want, but due to the way the software's build process has been set up, changing it in the .vdproj file was insufficient -- there was also a MyProgram.variables.wxi file that was used in the build process, and it contained its own copy of the UpgradeCode value. Once I changed the UpgradeCode in both places, the disassociation was successful.
I'd like to start playing with the latest versions of Typescript but I have production code using 0.82, and I don't want to switch it until I have checked out the new version (we use lots of modules).
Can multiple versions on a machine play nicely?
This isn't supported in Visual Studio. Best you could do is just install/uninstall on an as-needed basis.
If you just wanted to try compiling things on the command line, you could use the NPM package and download specific versions that way.
I am trying to install an Amazon Web service gem into my project (I use window and Aptana RadRails) but it asked me to update current Ruby version (1.8.5) to 1.8.7.
I use InstantRails for Window platform. So could you tell me how can I upgrade my Ruby to new version?
Do I need to install new InstantRails? or Can I update with Ruby Gem? or may be there is your alternative idea for this activity. :)
Thank you.
Ruby-lang.org Downloads The 1.8.7 binary is right there.
Even better than the builds on ruby-lang.org is the preview versions of the Ruby Installer built with mingw which allows compiling of gems without Visual C++ 6.0.
http://rubyinstaller.org/downloads/
Tutorials