Comments on: Compiling Inkscape: Update http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/ Thu, 08 Jan 2009 11:59:48 +0000 http://wordpress.org/?v=2.7 hourly 1 By: simarilius http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1276 simarilius Fri, 24 Oct 2008 19:45:57 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1276 You had trouble compiling on windows? Shouldnt be so. If ya ever want to try again stop by the jabber room and we'll try sort it for you. You had trouble compiling on windows?
Shouldnt be so. If ya ever want to try again stop by the jabber room and we’ll try sort it for you.

]]> By: Richard Querin http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1161 Richard Querin Thu, 03 Jul 2008 13:08:57 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1161 Sorry, that last sentence should read "clean, working compile". I think getting it to build and work properly should happen before you even attempt building the deb. You go girl! ;) Sorry, that last sentence should read “clean, working compile”. I think getting it to build and work properly should happen before you even attempt building the deb.

You go girl! ;)

]]> By: Richard Querin http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1160 Richard Querin Thu, 03 Jul 2008 13:07:30 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1160 I just checked what I do for the Task project. In this case, I download a tar.gz file (task-1.3.1.tar.gz). When extracted, this creates a folder called task-1.3.1 which contains the INSTALL, AUTHORS, INSTALL and other files along with a "src" folder which contains the source. So looking at Inkscape's svn trunk, I would roll that directories contents (along with the subdirectories src, share, po, etc.. ) into one big tar.gz file called say inkscape-x.xx.tar.gz and then follow the ubuntuforums posting that I pointed to. Not 100% sure it will all work properly, but that seems to be the way that article works with it. Maybe Inkscape provides a nightly tar file already? In any case, the fact that you can't get a clean compile on your machine is likely the sticking point here anyway. :( I just checked what I do for the Task project. In this case, I download a tar.gz file (task-1.3.1.tar.gz). When extracted, this creates a folder called task-1.3.1 which contains the INSTALL, AUTHORS, INSTALL and other files along with a “src” folder which contains the source.

So looking at Inkscape’s svn trunk, I would roll that directories contents (along with the subdirectories src, share, po, etc.. ) into one big tar.gz file called say inkscape-x.xx.tar.gz and then follow the ubuntuforums posting that I pointed to.

Not 100% sure it will all work properly, but that seems to be the way that article works with it. Maybe Inkscape provides a nightly tar file already?

In any case, the fact that you can’t get a clean compile on your machine is likely the sticking point here anyway. :(

]]> By: heathenx http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1159 heathenx Thu, 03 Jul 2008 11:46:05 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1159 I still do not understand. I get that you are making a deb from a source package but what I don't get is where my source package for Inkscape is located. I checkout the entire trunk via SVN. When I do this I get a "scr" directory among many other directories. Is this "src" directory the one that I need to roll up into a tarball or something? If I could just muster a half-ass way of making a deb to get my feet wet then I would be satisfied. I tried compiling from scratch on my Ubuntu home box last night. I checked out the latest version at the time (19116) and version 19107 (the version that worked on my Ubuntu box at work) and I could get either version to work. Let me clarify...both versions compiled without errors but when starting up Inkscape I got a warning dialog and the program shuts down after clicking the ok button. At least it compiles. Not sure why it wasn't working for me a week or two ago. I still do not understand. I get that you are making a deb from a source package but what I don’t get is where my source package for Inkscape is located. I checkout the entire trunk via SVN. When I do this I get a “scr” directory among many other directories. Is this “src” directory the one that I need to roll up into a tarball or something?

If I could just muster a half-ass way of making a deb to get my feet wet then I would be satisfied.

I tried compiling from scratch on my Ubuntu home box last night. I checked out the latest version at the time (19116) and version 19107 (the version that worked on my Ubuntu box at work) and I could get either version to work. Let me clarify…both versions compiled without errors but when starting up Inkscape I got a warning dialog and the program shuts down after clicking the ok button. At least it compiles. Not sure why it wasn’t working for me a week or two ago.

]]> By: Richard Querin http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1157 Richard Querin Wed, 02 Jul 2008 20:33:13 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1157 No it doesn't matter if the package is already installed. The process that I follow really involves working with the original source package. Then you prepare it in a certain way in a separate folder and do the compile as part of the process. It generates a deb file. It doesn't install anything. For instance I've packaged up this 2 or 3 versions of this Task program with a sub directory containing the source code etc. for each one. Nothing gets overwritten. It's not like Checkinstall where it installs the program and generates a deb file as a side-effect. With this method, there is no install to your system. You're strictly generating a deb file. (which you could then install on your system when you're all done). As far as being cold and scared, you really should be nicer to your wife. Or your secretary. ;) No it doesn’t matter if the package is already installed. The process that I follow really involves working with the original source package. Then you prepare it in a certain way in a separate folder and do the compile as part of the process. It generates a deb file. It doesn’t install anything. For instance I’ve packaged up this 2 or 3 versions of this Task program with a sub directory containing the source code etc. for each one. Nothing gets overwritten. It’s not like Checkinstall where it installs the program and generates a deb file as a side-effect. With this method, there is no install to your system. You’re strictly generating a deb file. (which you could then install on your system when you’re all done).

As far as being cold and scared, you really should be nicer to your wife. Or your secretary. ;)

]]> By: heathenx http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1156 heathenx Wed, 02 Jul 2008 19:59:46 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1156 Well, does it matter that the package is already installed? I have a build directory called "inkscape" in my home directory and then I installed it to an "opt" directory in my home directory. Do I need to roll something up into a tarball first? I feel like I'm sitting on a continent's worth of crude oil and I don't know how to get it to the people. I'm cold and I'm scared. :) Well, does it matter that the package is already installed? I have a build directory called “inkscape” in my home directory and then I installed it to an “opt” directory in my home directory. Do I need to roll something up into a tarball first?

I feel like I’m sitting on a continent’s worth of crude oil and I don’t know how to get it to the people. I’m cold and I’m scared. :)

]]> By: Richard Querin http://screencasters.heathenx.org/blog/2008/07/02/compiling-inkscape-update/comment-page-1/#comment-1155 Richard Querin Wed, 02 Jul 2008 19:46:22 +0000 http://screencasters.heathenx.org/blog/?p=180#comment-1155 While I'm definitely no packaging guru, I have made several packages for Task which is a command line todo list application that I use all the time. The first time out I used Checkinstall, but this is not really the right way. Now I do them in a more "proper" way. But mind you this is a little package that compiles in about 30 seconds. I posted about it here: http://blog.rfquerin.org/2008/06/17/building-debian-packages-for-task/ The article that I followed to build a proper debian package is here: http://ubuntuforums.org/showthread.php?t=51003 It's not rocket science, but the first time after about 20 minutes I had a proper deb package. I've used the method 2 or 3 times since and the article is relatively concise and understandable, even to a blockhead like me. :) While I’m definitely no packaging guru, I have made several packages for Task which is a command line todo list application that I use all the time. The first time out I used Checkinstall, but this is not really the right way. Now I do them in a more “proper” way. But mind you this is a little package that compiles in about 30 seconds.

I posted about it here: http://blog.rfquerin.org/2008/06/17/building-debian-packages-for-task/

The article that I followed to build a proper debian package is here: http://ubuntuforums.org/showthread.php?t=51003

It’s not rocket science, but the first time after about 20 minutes I had a proper deb package. I’ve used the method 2 or 3 times since and the article is relatively concise and understandable, even to a blockhead like me.
:)

]]>