Gtk Windows Software Distribution And
I just don’t get it at all. No, I don’t hate them, but there was a time when the term A software distribution and building platform on Windows doesn’t make sense to me. Tr u st me, I had a hellish time with stuff like Cmake, MSYS, MinGW, on Windows. A
I chose rust gtk because I know someone else on hackernews did it so I thought I'll be treading ground that has already been softened!I was planning to write my code on Centos 7 but it looks like due to mingw, which is the windows development libraries, being insecure, it became a giant pain to actually install the libraries needed to do cross compiling on my machine. In particular, do not use GTKWINDOWPOPUP just to turn off the window borders use gtkwindowsetdecorated() for that.I'm going to be taking a stab at writing a gopher client GUI application so I figured I'd just get started with it. Nearly all windows should be GTKWINDOWTOPLEVEL. GTKWINDOWPOPUP is used to implement widgets such as GtkMenu or tooltips that you normally don’t think of as windows per se.
I haven't looked at the code besides the very gist of it, which is that this program will create a small window with a button that says hello which will also print clicked when the button is clicked.This is now enough for us to test if out cross compiling will work.Now let's get to the harder part. This is quite different from the usual way I bring in dependencies and it would be good to find out why.Use gtk:: Some("com.github.gtk-rs.examples.basic"),).expect("failed to initialize GTK application") Let window = ApplicationWindow::new(app) Let button = Button::with_label("Hello, World!") Voila! We have out test gtk program. The example is what had lulled me into a false sense of confidence.The first thing we do is update our Cargo.toml with our dependencies. This is completely stolen from the rust-gtk website and is a basic example.
Gtk Windows Dll So That
Gtk Windows Exe So That
This will help when we go to package up our exe so that we can run it.We can use the -t option to get the paths of the dll so that we can then copy them.Once we have pldd setup, we can then add package.sh to our image. BashHere we can see all the dlls that we need for out gtk-test-3.exe. This will give us peldd which we can then use to find which dlls we need for our exe. DockerfileRUN dnf install -y git cmake file gcc make man sudo tarRUN dnf install -y gcc-c++ boost boost-develRUN mv /root/pe-util/build/peldd /usr/bin/pelddRUN dnf install -y mingw64-winpthreads-staticRUN /home/rustacean/.cargo/bin/rustup updateRUN /home/rustacean/.cargo/bin/rustup target add x86_64-pc-windows-gnuADD cargo.config /home/rustacean/.cargo/configENV PKG_CONFIG_PATH=/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/ENV GTK_INSTALL_PATH=/usr/x86_64-w64-mingw32/sys-root/mingw/Our docker image is going to use the latest version of fedora and one of the key things we need to build is peldd.To do this we first set up the system and get the usual things installed.Next we pull pe-util and build the project.
TomlWe also set environment variables so that rust will link the correct libraries that the windows executable will need.Finally we set a volume on our image which is where we will mount the external project we are working on.The last step in our Dockerfile is our package.sh script which will get run. Next we bring over cargo.config into our image. The first thing we do is add a windows target to rust. We then create a folder and copy the exe and dlls to our package folder.We also have some defaults that we need to set for out gui application.The final mingw-strip commands will bring the executable size down quite a bit.Now that we have our packaging utility installed and set up, we can now turn to installing the windows libraries we need to do gtk development.Here we install a whole slew of mingw libraries and we are almost off to the races.The next step is to install rust and this we can the usual way of using the rust script.Once we have rust installed, we now need to set up rust for cross compiling. Bash/home/rustacean/.cargo/bin/cargo build -target=x86_64-pc-windows-gnu -releaseCp target/x86_64-pc-windows-gnu/release/*.exe packageExport DLLS="peldd package/*.exe -t -ignore-errors"Cp -r $GTK_INSTALL_PATH/share/glib-2.0/schemas package/share/glib-2.0Cp -r $GTK_INSTALL_PATH/share/icons package/share/icons* Note - the export DLLS command should use ticks not quotes.We use our script to build our rust program. This will allow us to copy the file over to Windows and run our exe.
It should also be clickable and once clicked it should print out a message to the console.With that we are done! We have a working build system now and we can move to the actual application. This way we can see the cargo build process and any errors.Now our final command should have generated a folder called package in our current directory and when we copy that file over to a windows machine we should be able to run it and get a window that simply says hello world. Now we have the container ready to go.The last command is to start the gtk-test container and -ai will output the Dockerfile's output to the screen.
0 kommentar(er)
