I am trying to install 'David's Batch Processor' in order to batch convert multiple very large folders of RAW images to jpeg. I have tried using this guide to install the plugin, but it is very unclear what files I should move and where, since none of the files provided on the DBP website are saved as .py or SCM. The DBP website says I need "g++ and the gimp development packages for the appropriate Gimp version ". I have never used g++ or used any gimp development packages before. I feel like I'm way over my head but would like to learn how to do this!
g++ is a C++ compiler (actually a thin front-end over gcc).
Normally you would just do make; make install but this requires some other tools such as make that are part of the build-essentials package on Linux.
DBP has a competitor (or successor, since DBP updates seem to have stopped in 2013) called BIMP, and its GitHub page has instructions to build it on macOS. And even if you prefer DBP these instructions may apply in good part to DBP.
Related
Recently I implemented Box2D to our in-house game engine using C++11 and SDL2. A fresh install of Box2D will produce a x64 build. The engine had been built to run in x86 years prior so changing the architecture of the project just to match Box2D was out of the question.
I found a way to build in x86 that worked for me, so I wanted to post this as documentation to help out anyone struggling in the same way. If there is a better way to do it I welcome discussion on the topic.
So, how do I get Box2D to work with my project already built in x86?
First, you'll need to install Box2D [Box2D - C++]. Open up the command prompt and clone the repo onto your computer, I chose to clone this at 'C:\temp\'
After you've finished pulling down the project, navigate inside the 'box2d' folder and run the build.bat script. This will install/compile everything you'll need to start working. The only downside is that it will build in x64 which might not work for everyone (if x64 works for you, you can stop reading. Congrats!)
Second, if it isn't already, install vcpkg. You can follow [this vcpkg guide] up to step 2 (Run the bootstrap script to build vcpkg). For convenience's sake install this at 'C:\temp\' too.
Once set up is done, use the command prompt to navigate into vcpkg directory. Then run the following:
vcpkg install box2d
This will run another installation, once it's finished navigate to [path\to\vcpkg]\installed\x86-windows. Here you should find all your new lib and include files for Box2D.
Now you have the freedom to move these files wherever you need to for your projects. Edit your project's properties as needed and you'll be able to successfully run your code in x86!
I made an application using GTK3 on Windows (Mingw_x64 installation of GTK) and I cannot really figure out how to make a distribution out of this. According to official documentation of PyGObject, it is possible in some way.
I already tried to make a package using setuptools, but PyGObject documentation is not saying much about this process and I was not able to configure setup correctly to make it work. PyGObject has a lot of dependecies and weird imports, that I do not know how to include.
I also tried Pyinstaller, which claims it has GTK support, and it really can pack it into executable, however it is not working. I tried these two options:
make only one file (.exe), but in this situations, it throws an error, that some file is not found (libpixbufloader-ani.dll)
create a directory with all needed files (libpixbufloader-ani.dll and other libs are included this time), but when running exe, another exeption occurs, this time Struct and 2 other libraries are missing (strangely, there is a folder that contains Struct)
Becouse of the missing files, I tried adding as many paths containing needed libraries as possible to Pyinstaller, but without success.
Does anyone have any experience with packaging GTK appliciations in Python? There is definitely a way to do this, but I am not very experienced with packaging. If needed, I can provide more information.
This is an issue that has been brought up on PyInstaller's GitHub page, as others (including myself) have experienced the same issue that you've mentioned.
The last time I tried the dev version of PyInstaller, the issue still wasn't fixed, but I managed to get a working executable by using PyInstaller to find the dependencies that my Python3/GTK3 app needed, and then I used cx_Freeze to generate the final executable.
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
edit: The real solution to this is now that OpenCV supports python 3. I'm leaving the details below for anyone who happens to be stuck with an old setup.
I'm trying to get OpenCV working with Python 3. A friend showed me ctypes-opencv that appears to work with Python 3. The problem is I totally can not figure out how to "install" or get any code working. I've followed all instructions I could find from a few people mentioning installs on google and none of those seemed to work or I couldn't even get through the basics that they mentioned.
I am just hacking around with the version of IDLE that came with Python 3. No IDE.
Start with OpenCV:
The only windows installer for OpenCV 2.1 is a visual studio installer. I assume that means that it installs files that make it easier to use in Visual Studio. However, does it also mean that I can't use that installer with Python 3? I tried the vs installer together with ctypes-opencv as below, and I got errors that the dlls were not in my path (but my path variable did include the OpenCV bin folder with dlls). Is this the wrong direction?
The apparent alternative is to build OpenCV myself. I tried following the directions here and all I get is "project files may be invalid" from the CMake gui application when pressing the "Configure" button. Same when following these hints from Stack Overflow. I'm suspicious that this is also the wrong direction since I am not currently using any of the tools that are listed in the CMake configure. Is this also the wrong direction?
Next ctypes-opencv:
I installed this and the installer recognizes Python3.1 and puts itself into the site-packages folder. If I try to run demos, it tells me the dlls are not in the path although they are, as mentioned above.
Summary:
I think I generally understand each piece here (code, compile, dll, imports, ...) but I do not know how all the pieces fit together and where I am going wrong. Can someone please tell me what steps or understanding I am missing here?
I get the feeling that I need to be reading a book or two to fill in the holes in my understanding of how all these pieces fit together. I wouldn't even know what area of books to get though so any suggestions there would be appreciated as well.
Python's ctypes is a wrapper around the opencv dll files, as long as you can point to the compiled libraries it doesn't matter what the source code is set up to be edited in. For windows I would simply run the installer, then try to load the dll with ctypes. If you can get that far, any other errors can be fixed by looking at the ctypes wrapper file and editing the load section to look like your test file.
Christoph Gohlke maintains Windows binaries for many Python packages, including the production version of OpenCV 3.0 with Python 3.x bindings, released 4 June 2015:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#opencv
To install, just download the 64-bit or 32-bit .whl file appropriate for your system, then run pip install [filename]. Then the instruction import cv2 should work in your Python 3.x interpreter.
Yakiimo san, OpenCV 2.1 DLL can be loaded with ctypes. I have tested it.
p.s. I have set the C;\OpenCV2.1\bin in Env Path.
Recently when I have found good sources packages for ghc 6.12/6.10 on Hackage I've been forced to do some minor or major changes to the cabal files to make those packages to work under windows.
Besides to fork and merge my fixes with github, what seems to be the best way/ good enough practice to take these modified builds to a couple of other windows boxes that only has a basic haskell platform installed?
I should prefer if I somehow could work with the cabal-install because that is what one normally use.
Should one put the modfied build dirs on a shared/networked dir and mount from the targeted windows box?
Say something like this:
on machine prepare
cabal fetch foo
cabal unpack foo
cd foo
edit .cabal and .hs
cabal configure
cabal build
On machine useanddevelopnormal
cd machinepreparemount
cd foo
cabal install
The Yackage tool allows you to run a local Hackage-compatible server easily. You could deploy your modified versions on Yackage, add the Yackage repo to your repository list and then use cabal install as usual.
Using github is certainly "good enough" although if it seems to be a regular operation that you do in order to get something working on Windows, you may want to mention it on the development mailing lists for GHC, or at least on haskell-cafe. If this procedure is minor enough, if may need to be incorporated into general builds.
Definitely, working with the cabal-install is suggested. However you are able to distribute your personal fixes is a private matter, and not meant for others to control.
In principle it is possible to make local hackage archives and to point cabal-install at it. However currently we do not have very good tools for producing the archive format. If you have the time, it's a matter of getting the right directory layout and using tar to make the index.