I apologize in advance for the stupidity of this question, but I am confused as h#&! and not even sure what to ask anymore.
For my math thesis - i.e., I am not a programmer - I have to write C code which uses the CVODE library, which is part of SUNDIALS (do you need all that detail?). But I can't work directly on the Gentoo Linux cluster where the proram will ultimately run.
According to the SUNDIALS' website, CVODE has very rarely been compiled and used in a native Windows environment, but it has been used using Cygwin. So I want to set up a C programming environment, including an IDE (especially a debugger), on my Windows PC, using Cygwin.
I have installed and executed the basic Cygwin (plus a package for nano editor) on my 64-bit Windows PC. I want to use Eclipse IDE, which is available for Linux and Windows, and can really only be used in a graphical interface (I think). I think I should set Eclipse up next (and then CVODE after that). That's what I'm trying to do now.
My basic question is how do I setup Eclipse to work with Cygwin? What Cygwin packages do I need to run Eclipse?
From the docs, I see that Cygwin has a server (Cygserver), but does not have a graphical interface. Or, it might have a graphical interface called Cygwin/X. Do I setup Eclipse in Windows to communicate with Cygserver, then do my work in Windows, but compilations and so forth would take place in the Cygserver? Or, do I install Cygwin/X and use a Linux version of Eclipse which, hopefully, works with Cygwin/X? If both are possible options, which is easier (I'm guessing the latter).
Cygwin is nice but I've run into issues now and then with it. I would recommend that you download Virtualbox or some similar VM software and install the same Linux that is there on your production cluster inside it. Then you'll have an environment on your development machine which matches the production one.
Now, install eclipse (and anything else you want) inside the VM and you can develop the software there smoothly without worrying about tangential issues like cygwin and the rest.
Related
I would like to try scidb as a replacement for hdf5. I would like to test it on my Debian laptop (no clusters) to give it a try.
Is this possible? Might be that Debian (as opposed to Ubuntu) is not supported?
I had no luck with the installation instructions. The deployment script tells that my OS is not supported. The scidb userguide says about some pre-built packages (for Ubuntu, at least). But there is no hint on how to obtain them.
SciDB is limited to RedHat / CentOS, and to Ubuntu as of the 14.9 release. Folk who want to run it on other distros generally compile from code.
Information about how to obtain the sources (as well as current documentation and community discussion) can be found on the forums here ... http://www.scidb.org/forum/. You'll need to register as a forum user.
Specifically, have a look at http://www.scidb.org/forum/viewtopic.php?f=16&t=364. There's a list of releases and links to code bundles there.
I installed SciDB several times using several ways (building from sources and installing from packages, installing the cluster version and the dev version).
Installation from packages
First, if you choose to install from packages (the easiest and fastest way), SciDB is very very sensitive about your Linux version. For example, for the last version of SciDB (14.8), if you choose to install on a Ubuntu, it has to be a Ubuntu 12.04 (and not a 14.04, a common mistake) 64 bits (meaning you have to install the AMD64 version even if you have an Intel processor). It won't work if you have a different version.
If you have an Ubuntu 12.04 AMD64, Paradigm4 provides a deployment script and a documentation with very simple steps:
https://github.com/Paradigm4/deployment
Installation from sources
It's not so difficult but it can be painful and time consuming. I did it because we had to compile a custom plugin for SciDB. You have two types of installation: dev install (in SciDB user directory) and cluster install (in /opt/ directory).
You have to be registered on their forum to have the link to the source code. They provide a specific documentation to build from source.
Good luck.
Several months ago I have dealt with porting SciDB 14.12 to an unsupported Linux - Fedora 19. If your OS is not supported, it will neither be supported if you try to install from the sources. You have to start from the sources, but then you have to adapt the deployment and installation scripts. The sources can be downloaded from SciDB forum.
Namely, add a new platform to deployment/common/os_detect.sh. Then, there are multiple platform specific deployment scripts, such as deployment/common/prepare_toolchain.sh, deployment/common/prepare_coordinator.sh and deployment/common/prepare_chroot.sh. You need to make sure those prepare the environment as they would on the supported OS'. I used Red Hat 6 and CentOS 6 as a reference, as those are both more similar to Fedora. Since your OS is Debian, you can first try falling back to Ubuntu deployment (in os_detect.sh).
Another problem you may encounter are the 3rd party tools, specially Boost. In my case, I had to build it manually from sources.
Sometimes when porting and debugging it is not convenient to run the scripts with deploy.sh, but it's better to run the deployment scripts directly on the target machine (e.g. coordinator).
Probably the best way to install and to start with SciDB is to download a standard image. With this image you only have to import the virtual machine with a software to virtualize. Moreover there are some characteristics of this virtual machine that are great to develop your first applications.
The main advantage, is that you have an API to SciDB queries and another to R. Then you can explore all options and to test SciDB.
This is the version that I downloaded few months ago: http://www.paradigm4.com/forum/viewtopic.php?f=14&t=1329&sid=606f614e401900cfa750375ba56de656
Nevertheless, there is a problem, the community is too poor. There are little people developing with SciDB.
I want to develop in the Go Language (go-lang) using Google App Engine to run my app and I use IntelliJ on Windows. How can I do this?
If you use the official installer, it is very easy to get Go up and running on Windows.
Edit: The latest Zeus beta now has support for the Go Build, Format and Run commands and also does Go initellisene (i.e. auto complete).
Edit, Jun 2012: As at the 1.7 version, there is now experimental support for windows:
https://developers.google.com/appengine/downloads
The Go App-Engine development server is available for Linux and Mac only [1]. The Go language is available for Windows, but not the app-engine tools. I imagine it would be possible to port the GAE dev server to run under windows, because it just uses python, go and sqlite, but I don't think anyone has done so.
Of course you can run a linux virtual machine, or remote into a linux server to do the development. You could even edit in windows using sftp if your editor supports it.
[1] https://developers.google.com/appengine/downloads#Google_App_Engine_SDK_for_Go
You can find golang builds for Windows here. Golang is primarily focusing on unix-like OSs (golang devs are from bell labs), but while writing an application for appengine you won't hit any issues because you're using a Window's version. The appengine platform doesn't let you do things like manipulate files: instead you use the appengine's datastore/blobstore to store things. The main issues the Window's golang port are related to simply operating system functionality and since you won't be using any on appengine, there's no issue.
As for an IDE on Windows that has code completion, goclipse probably has the most "out of the box"; it's distributed with golang plugins and autocompletion. Golang itself is distributed with plug-ins/configs for the most popular editors (vim, emacs, sublime, etc...). You can use pretty much any popular editor with nsf's gocode for autocompletion if you want to take a little time to set things up.
The development for golang is pretty quick; I'm actually turned off from using appengine until it supports Go 1. There are some big changes between r60 and the current golang. Most libraries are keeping up to date with the quick golang development, which causes some pains using r60 golang.
There is a Windows version of the go toolset, you will have to install that from golang.org.
You can start with goclipse. If you don't like Eclipse, then you can use Emacs (available from gnu.org) for Windows; or any editor that you like.
Go on Windows isn't fully supported yet. Another option would be to download Virtual Box; install Linux on a virtual machine and use that as your development machine.
I want to write software for the Linux platform, but I would like to do this on a Windows OS. I'm only developing Linux software for a remote server of mine, so it wouldn't be worth it to switch to Linux just for that. I don't think it's as simple as using a cross-compiler, because I will be writing code that uses headers specifically for Linux, and I would like to test the programs on Windows. I don't want to use VirtalBox etc.
If possible, install the entire development environment on the linux server. Then install an Xserver (e.g XMing) and an ssh client (e.g putty) on your Windows box. Then run the dev. environment remotely.
The big pro of doing this is that the linux windows integrate seamlessly in the Windows enviornment. I used to work with dual platform development and had a virtual linux box on my PC. Still, I used ssh+X-forwarding to access it. This way I got full copy-paste support etc. between the environments.
Now WSL (also known as "Bash on Windows") exists, you can run native Linux binaries directly on Windows. With snapcraft you can package Linux applications entirely under Windows, without using a VM. Might be a better option. I made a super quick video to explain it.
CoLinux allows you to run linux side-by-side with Windows.
You could try VirtualBox and virtualize a Linux environment from within Windows. I do the reverse of what you are trying to do and run Windows from Linux, and it works quite well.
If you are familiar with .NET and C# you can use Mono for your client.
You can use Visual Studio to develop and the Mono runtime one Linux to run the application.
You do need to keep away from windows specific code.
Maybe Cygwin could help. You don't need an entire virtual machine and only the api is emulated.
You could use g++ in cygwin to target a linux binary. It's a pain to setup as you noted you'll need the entire toolchain (not just the compiler). I've used crosstool (domain name makes me giggle every time) in the past with success. It looks like someone did the work already http://metamod-p.sourceforge.net/cross-compiling.on.windows.for.linux.html
However I've never targeted linux from windows. I'd install a virtual linux box, way easier and you're likely going to want to do your testing on a real linux box before going live.
Cygwin isn't linux so you can't test your linux binaries there.
Out of curiosity what's keeping you from doing the development on linux? If the server the app runs on isn't mission critical you could even develop there.
we have a small app that doing trivial stuff, no GUI.
we was using Linux, but the library/framework available for Linux is highly less than that for windows, it was such a pain to develop under Linux.
So we want to use windows, but windows is too big for the trivial app, is there any solution that i can use windows and not losing OS's lightweight?
any advices appreciated.
What kind of applications are you building?
1) some older versions of windows have less bloat, but you wouldn't want these running on public networks because they don't get security updates. Plus, the latest/greatest libraries may not run on them
2) If you're running command-line server utilities, you could try Windows 2008 Server Core, which is a console-only installation
3) You might want to try Wine or Mono to run your windows/.NET framework-based application.
You should try a "Windows PE" (sometimes also called "minint") installation (installation guide here), which is a trimmed-down version based on Windows XP or Vista.
This does not make sense, sorry. If you have a CLI program under Linux why shouldn't you be able to write on CLI program on Windows?
I've been a Visual C++ user for quite some time now, and in the following weeks, I will be joining a (C++) Linux-only project. It should be noted that I have absolutely zero development experience on Linux.
Currently, Visual C++ 9 along with the Visual Assist X add-in make Windows-based development rather enjoyable. Having looked at various C++ IDEs on Linux left me a little disappointed with the coding experience, however.
I'd love to be able to use my current tool set (see above) for Linux development, so I have a couple of questions:
Can the VS editor convert between CR+LF <-> LF in a reliable manner?
Is it possible to set up a system where if I press "Build" in the IDE all of my work gets transferred to another box (e.g., a virtual machine) running Linux that compiles my project?
How would debugging work? Is it possible to remote-debug an application running in Linux via something like gdb? If so, would the "advanced" features of MS's debugger (e.g., tracepoints, break-if-cond, etc.) be lost?
Is this even a sane thing to think of? Does anyone use a Windows environment for Linux development? If not, I guess I should just suck it up and move to a Linux environment all together...?
Any input is appreciated, as I feel a little lost right now.
It's probable you'll eventually want to suck it up and work on Linux. microsoft, for obvious reasons, builds their tools to be very Windows-centric and Windows-specific; there are even a few ways in which Visual C++ isn't quite standard C++.
That said, though, you can work with VC++ to some extent.
There are easy tools on linux that will translate to UNIX line endings from Windows. (called something creative like 'dos2unix')
You can set up a remote file system, like with ExpanDrive for Windows, to let you keep your files there.
You can run ssh or rsh from Windows to run makes on the remote Linux box.
I've done windows/linux/freebsd cross-platform development with Windows as my primary OS... so it is possible.
Use VS as editor.
Access Linux Dev node via SSH with
putty.
Use revision control system
(subversion/git/bazaar/mercurial/cvs)
to check changes into repo & check
changes out on Linux.
Use a multi-platform build process. I
use SCons. It is python based
and works beautifully - though it is
a little slow with the default
settings.
Launch build process from shell using
putty.
Use additional shells as needed to
attach gdb & debug.
Now to answer your questions:
Yes. There is a VS setting to say use unix line endings. Many revision control systems can also be configured to correct this for you.
Maybe, but that's not how I did it.
Yes, you can remotely debug using GDB. GDB has many (all?) the features available with VS's debuger but you have to learn the GDB commands. I don't know of a way to use VS's debugger to debug processes compiled with GCC - though this is a frequent request.
I'd recommend that you dive in and try to learn the Linux way of doing things. What are the other people on your team using? If you use the same tool-set as other people, you'll be much better of when asking for help. If you're sitting on a Windows box cross-compiling using Cygwin, you're more or less on your own.
I work on a Linux team currently but use Visual Studio + Visual AssistX as my IDE. VS+VAX is the best environment for developing code in my opinion. Nothing like it exists anywhere else that I've found.
What you want to do is:
Install Cygwin openssh and configure it for shelling into your linux machine without a password.
Expose your development tree on your linux machine as a samba share and mount the share on your Windows machine.
Create a Visual Studio "makefile" project referencing the files on your linux machine.
Override the make command to ssh into your linux machine and execute the build.
Write a sed script on your linux machine that converts gcc/g++ output errors into visual studio format. I use something similar to this: sed -e 's/(.):([0-9]): (.*)/z:\path\to\code\\1(\2): \3/' \
I would really recommend you to give Linux a shot natively, not through a virtual machine. If you run it under a virtual machine you will probably end up doing 85% of your activities under Windows and this will prevent you from actually learning anything under linux.
Install linux in its own partition and work on it fulltime. Do this ASAP before the project start and get familiarized with the basics on how to use it first.
Regarding IDE's to use, find out what build system the project will use and what libraries you will be using. KDevelop is a great IDE although it might be a bit too cluttered. I really like Qt-Creator.
You might wanna give Eclipse a shot too.
As of what distribution to use, I would recommend you Archlinux if you feel like really learning something out of this and learning about linux along with learning to do development under linux. If you dont really want to learn too much about linux and go straight into developing then go with Kubuntu.
As for what Desktop Manager to use I would go with KDE.
There is no Visual Studio on Linux. Period. Try KDevelop or Code::Blocks. They should make development fun on Linux.
As for the compiler/executables you'd have to use the GNU GCC toolchain. There is no MS cl compiler on Linux either.
The debugger to use is gdb, again part of the GCC toolchain.
One more thing, try to pick a shell (like bash) and read up on it. It'll save quite some time in future.
I wrote a ftp script to move files from my pc to the linux box,
then set it up as a tool, so i can at least write the code on the pc, and have
easy access to source safe. I hit a tool button, and the files get transferred to
the linux box, where i use the utilities there to do the work
& 3.:
I use cygwin + Eclipse on Windows for developing and compiling.
With this combination I can also debug via gdbserver on the target machine (VM with x86 Linux or ARM "real" target).
Unfortunately you have to do some tiny but important settings (library paths in gdb etc...) but as soon as it works......
Sorry, no solution for debugging from within VS on a linux box...and I think there will none in the near future...
What you will find is that there are dialectic variations in the compiler and the libraries are different enough that it's unlikely to work well.
You're probably better off with a gcc based tool chain like MinGW if you don't want to switch your environment to Windows right off. MinGW uses native Win32 ports of standard open-source libraries such as getopt, and it is fairly easy to port software between Linux and MinGW32 (as long as you're not using Linux or Windows specific APIs).
However, porting software from MinGW to Visual C++ is quite a bit harder. On the few occasions that I've done this sort of thing I find that porting between Linux and MinGW is much easier than porting between MinGW and Visual C++.
As far as I'm aware I've never seen a MinGW plugin for Visual Studio, although one could theoretically write such a thing as Visual Studio will let you use third party compilers. Additionally, you will have to work with whatever build system the rest of the team uses, which is pretty much guaranteed not to be MSBuild.
So, I'd guess that it's fairly unlikely to work well. Still, as Hunt & Thomas would say getting used to a different way of doing things will make you a better programmer. While vi (or emacs if you're that way inclined), ctags and gdb work quite differently to Visual studio they're still quite a powerful development environment. With MinGW32 and Cygwin or MSYS you can use these without having to make a wholesale switch across to Linux.