Re: [gedit-list] Tutorial On How To Build Gedit

[Jeff Johnston <jeff johnston mn gmail com>]

Which distribution do you use? I tried for the better part of a day to get gedit built from the git repositories with no luck. I use Ubuntu 10.10. 

Way too many problems to post. At times I was modifying source code to get it to compile just to get further, but really the dependency issues proved to be more work than it was worth. In the end I figure I am better off just working on the latest (2.30.3)...unless there is a distribution that is more build friendly with the latest git repositories.

I like the idea of jhbuild...just wish it worked without any hitches.

I found this link which helped a little (in case it helps anyone else):
http://live.gnome.org/JhbuildOnUbuntu

-Jeff

On Tue, Aug 10, 2010 at 8:57 AM, Jose Aliste <jose aliste gmail com> wrote:

On Tue, Aug 10, 2010 at 9:49 AM, Jeff Johnston
<jeff.johnston.mn@gmail.com> wrote:
> It looks to me like you are trying to compile the latest gedit from the git
> repositories. To do that you would need to be using the development branch
> from gnome as all the dependencies are under development as well. I have not
> yet experienced trying to get the latest gnome running.
>
> If you want to build the latest production version of gedit then you can
> download the latest tar file.
>
> http://ftp.acc.umu.se/pub/GNOME/sources/gedit/2.30/
>
>
> -Jeff
>
>
>
> On Tue, Aug 10, 2010 at 8:29 AM, Larry Price <larry.price.ml@gmail.com>
> wrote:
>>
>> Hey Jeff,
>>
>> I was wondering if you could help me build my copy of gedit. I've
>> successfully built it in the past, but now I'm having a lot of problems. I
>> know most of these make it seem like I just need to install something, but
>> I'm not sure what:

If you want to build gedit development version, then the easiest way
is to use jhbuild [1]. Basically, you need to follow the steps in the
jhbuild manual and some hints.

1. You need to use gnome-suites-3.0 module set.
2.  Using jhbuild build gedit can be very slow since it will compile
all the dependencys, which are a lot, so what I do is to do

$jhbuild build gtk+-3
$jhbuild build libpeas
$jhbuild build gtksourceview
$jhbuild buildone gedit

Of course they are easier ways (there is a way of say to jhbuild to
ignore some dependencies when not building, but I do not know how to
do this).


Greetings,

José

PS: I used to hate jhbuild, and probably it will get you some time to
get used to it, but once you do, it makes your live easier. Specially
for this dev cycle.

>>
>> "Requested 'glib-2.0 >= 2.25.12' but version of GLib is 2.24.1
>> Requested 'gio-2.0 >= 2.25.11' but version of GIO is 2.24.1
>> No package 'gtk+-3.0' found
>> No package 'gtksourceview-3.0' found
>> No package 'libpeas-1.0' found
>> No package 'libpeasui-1.0' found
>> No package 'gsettings-desktop-schemas' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables GEDIT_CFLAGS
>> and GEDIT_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details."
>>
>> Do you have any advice?
>>
>> On 8/9/2010 11:40 PM, Jeff Johnston wrote:
>>
>> I have a tutorial on how to build a local copy of gedit. This was
>> something that was not obvious to me at first so I was hoping I could help
>> someone else.
>>
>> http://code.google.com/p/codeslayer/wiki/HowToBuildGedit
>>
>> -Jeff Johnston
>>
>>
>> _______________________________________________
>> gedit-list mailing list
>> gedit-list gnome org
>> http://mail.gnome.org/mailman/listinfo/gedit-list
>>
>
>
> _______________________________________________
> gedit-list mailing list
> gedit-list gnome org
> http://mail.gnome.org/mailman/listinfo/gedit-list
>
>