Goddamn.
That's all there is to say. At first I thought I was just really dumb in installing this thing, but the more I work trying to get this library up and running, I noticed that I've spent two days on doing such a trivial task.
And for the first time in ever (which is why this deserves a blog post), I give up on this. If anyone got this imaging library up and running on an x64 system let me know.
If other libraries are as hard to install as this thing, I'm going to jump out a window.
Nothing else to report. I'm totalling bitching right now. :/
Also, I'm curious as to what's everyone's favourite IDE is, personally I like using codeblocks because of dat simplicity. I always get overwhelmed by microsoft visual studio and too asspained by vi/emacs.
I can't solve this problem, but...
Quote:I always get overwhelmed by microsoft visual studio and too asspained by vi/emacs.
That's why you use Vim!
whjms Wrote: [ -> ]Quote:I always get overwhelmed by microsoft visual studio and too asspained by vi/emacs.
That's why you use Vim!
Well it's definitely something with a learning curve, might as well. Totally beats trying to figure out how to wade through a bunch of unknown options and pray that it'll work.
I always find that learning a tool seems to be a waste of time, but I probably wouldn't have ran into all this trouble if I knew what everything was in the first place.
Most libraries should be a 'apt-get install some-library'. Some are more difficult, depending on what it is of course. If there are pre-built versions of it, perhaps try those.
I find most IDEs just a glorified text editor >_> I'm probably not really using them right. Have only really used Visual Studio and Eclipse for some time.
I prefer Visual Studio actually...
I find it a convenient way to manage projects and all the files necessary for them...
I don't even use the IDE for half the things it is capable of...
Slushba132 Wrote: [ -> ]I prefer Visual Studio actually...
I find it a convenient way to manage projects and all the files necessary for them...
I don't even use the IDE for half the things it is capable of...
Yeah, I feel you on that one, that's why I use something really simple like codeblocks.
Like whjms said, vim is pretty nice because it's the epitome of basic and gets more advanced when you need it to. It does have a learning curve as soon as you start using it, so that'd probably turn most people off. When I did use it however, I can attest that it sped up my productivity because I was just blasting commands into the console and sped on my way without having to navigate through a bunch of folders to execute something or reading incomprehensible dialogs in some far off edge of the window.
Of course, I'm not using it now because I can't into linux, so (don't laugh at me) I'm reading a book on linux right now to get familiar with the OS and the whole consolan' that all you crazy linux dudes use.
Why does windows have to be the fun(games) OS :( .
Visual Studio for me, i used SWI-Prolog Editor for a while, which is Emacs based, annoyed the spoon out of me
ProperBritish Wrote: [ -> ]Visual Studio for me, i used SWI-Prolog Editor for a while, which is Emacs based, annoyed the spoon out of me
I'm just going the emacs/vim route because I want the neckbeard prestige.
I can't get into visual though, it's definitely damn diddly nice but the options overwhelm me and building simple programs in it isn't a simple process (at least for me, I haven't worked too much with it after I couldn't wrap my head around having a debugging window stay open when I hit debug).
How did you try installing it?
Le Jooms Wrote: [ -> ]How did you try installing it?
This is for a windows 7 install
Downloaded the build, unzipped it, got a program called cmake that apparently builds the binaries of the folder you just unzipped. Did that, navigated to the binaries it made, opened the .sln file it just put together, built that in microsoft visual studio. I then added this directory that was made to my environment variables PATH so that it could look up this folder when running functions from the library. Made a new project, linked the include directories (with the needed header files) to the project, linked the library directory to where the .lib's were located in the DEBUG folder. Went to the linker options and added the three libraries that I would need to write a simple program.
And it would just give a bunch of linker errors then normal application cannot run errors after I fixed that. I gave up by then.
Apart from setting the include, library and linker settings, I had no idea double you tee eff was going on.