I'm using msysgit on Windows 7, but it doesn't seem to come with make. Is there an easy way to get make running on msysgit?
I found a link to make.exe in the msysgit Google code issues section. I downloaded it and put it in Git\bin and it works perfectly.
Suprisingly, by using MSYS itself, or MinGW if you need the GCC compiler - see http://www.mingw.org or better http://tdragon.net/recentgcc.
did you try the netinstall ? It does come with make.
I'm going to guess that the msys.bat and initialize.sh step still needed to be performed.
The 'Full installer' isn't. It only gets you a minimum, and you then have to get it to do the remaining download - see MSysGit:InstallMSysGit. I just updated the wiki to highlight the steps I'd missed!
The Net Installer is a much better option as it is able to run through almost all the steps for you, downloading and compiling the latest version automatically. Once you have done so, have a look for the various release.sh files.
It can be a nervous first step choosing the right course of action - I'm only a few steps ahead, and still cautious.
Related
I wanted to install caffe on openSuse.
Just for the record - it worked out for me, I just don't know what's the "exact" way to do this. The things I did maybe aren't really for someone who's new to this, and also it was kind of a "bad installation". My way was the following:
First, I did
make all
This worked, until it complained that some libraries weren't found (libclbas etc.). So I used
ccmake .
to change the paths to the libraries manually. I needed to manually type the paths to the snappy, boost_python, blas, cblas and lapack libs. After doing that I did
cmake .
and then
make
and everything worked. My problem now is - why doesn't make find the libs, and is there a way to fix this? I think the problem was that I didn't have /usr/lib/libcblas.so but /usr/lib/libcblas.so.3, and similar "problems" with the other libraries.
Another thing - when I tried using ccmake/cmake right from the beginning (without the make part first), there weren't any files in my build directory (like $CAFFE_ROOT/build/examples or $CAFFE_ROOT/build/tools were empty), so the mnist tutorial for example wasn't working. That's why I first called
make all
, what may seem strange to you.
Of course I know how to fix this stuff, but I would like to know how the correct way for a "clean and simple installation" is. Did is miss anything when using make/cmake, is this some kind of inconsistency in caffe or something else? And, what is the clean way to do this?
Maybe look at the Ubuntu installation guide? http://caffe.berkeleyvision.org/install_apt.html
It mentions all the different packages you might need. I couldn't find openSuse installation instructions - but you should be able to translate the apt-get commands for your platform.
I want to build a GUI for some fortran code I have. GTK-Fortran seemed like a simple option, but I'm having trouble getting everything installed in the correct place.
I am using Windows 8. I have gfortran (version 4.8.1), Cmake, and GTK+ 3 installed. As far as I can tell, the last thing I need to do is include GTK-Fortran, which I download from https://github.com/jerryd/gtk-fortran (the link to download the .zip file is on the right side of the page), but all of the instructions on what to do with it are incredibly vague to me. The INSTALL instructions seem to want me to make a new directory, C:\build, and then do something with cmake, but I'm not sure what that something is or how to do it.
I have GTK+ 3 in C:\GTK, and its bin is included in the path. I would like to just put the GTK-Fortran files within the GTK folder, but I don't think that will actually give me access to the GTK-Fortran files.
Could someone give me very clear instructions on what to do with the files for GTK-Fortran so that I can call them from my own fortran code?
The simplest way for using gtk-fortran under Windows is to install MSYS2/MINGW64, following the installation steps described in the wiki of the project:
https://github.com/vmagnin/gtk-fortran/wiki#windows
I've followed these directions exactly.
I was able to compile mingw32-make ycm_support_libs and it produced the necessary ycm_core.pyd, ycm_client_support.pyd, and libclang.dll files. However, I get this message when starting vim:
YCM libraries found in old YouCompleteMe/python location; please RECOMPILE YCM.
I have verified that all the tools I've used are 64bit version. Anything I find on the web about this just says to run ./install.sh --clang-completer, which should be doing exactly what mingw32-make ycm_support_libs does.
I was so close too! Any help?
The file that is produced from the compile doesn't need to be moved. This was an old instruction that is now obsolete. I've managed to get C/C++ auto-complete working on Windows 7.
https://github.com/Valloric/YouCompleteMe/issues/1172
From the above link: Oh I see... sorry :P Anyway I don't know when was the last time someone modified the wiki page on installing YCM on Windows. The wiki page is community maintained. The error is caused by the fact that before YCM was splitted in two repo (this one for the vim client, and one for the general backend, ycmd) the compiled libraries were putted in YouCompleteMe/python now instead are putted in YouCompleteMe/third_party/ycmd. Anyway we can continue to discuss this but I have to close this issue since is not a YCM bug and Windows is not supported officially.
Sorry if I'm a bit of a noob when it comes to this sort of stuff, but thanks anyway.
Basically I've managed to install QT4.7 properly and it works and compiles stuff. (I'm using it conjunction with vs2010). However, I wanted to try something that requires libqxt. Unfortunately this seems to be the only installation guide out there. And I'm really not getting it. It mentions this little bit:
"configuration
Make sure qmake is in your PATH and run"
I think this is where I'm getting tripped up. Is this the qmake the same one I used for QT4.7? (If this is the case I shouldn't have to change anything right? It ought to look like this: "c:\Qt\4.7\bin". Which is added by going to >
Control Panel|System|Advanced|Environment variables menu. And which is already there from installing qt4.7)
Or is there a new qmake for libqxt somewhere? Am I understanding the term PATH incorrectly?
In any case right now clicking on configure.bat just echoes back "searching" and then closes before I can read what else it says. Would I be better off just opening a cmd prompt and cd'ing to the libqxt directory and running the configure file from there?
If anyone knows of an alternate install libqxt tutorial somewhere that'd probably helpful to me as well. Thanks to anyone who can take a minute to point me in the right direction.
I've tried to use MonoDevelop 2.4 and 2.6 with Ubuntu 11.04, but neither of them seems to actually provide any way of running the project. (As the picture shows, the Run, Step, and Debug items are disabled -- both on the toolbar and inside the menus.)
This is true for all project types I've seen so far -- C#, Python, etc...
But mono-debugger is installed. Is there some post-setup task that I need to do manually, for this to work?
Looking over https://github.com/mono/monodevelop/blob/master/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Commands/ProjectCommands.cs
Perhaps you haven't selected a 'Project'? Open up the Solution pad and click on the Test1 project (not the solution at the root of the tree, but the project just below it).
I'm just guessing here since I don't have Ubuntu and can't actually test anything.
Edit: actually, it looks like clicking on the Solution would work as well.
From looking at the code, another possibility is that you don't have a build target? Not sure how that would happen, but unless you only opened Main.cs and not actually Test1.sln, I don't know what to suggest.
When you opened the project, which file did you open? Test1.sln? Test1.csproj? Or Main.cs?
Try looking for mono-mdb and more packages in synaptic, this may fix this issue.
Don't remember exact names, Linux box at home...
Did you really open the project? It looks like you just opened Main.cs. It won't work that way.
Make sure you installed the compilers (mcs etc)