Unfortunately, those are the same steps I've been following, only I
haven't been specifying libdir. Is it necessary to run make and then
make install one right after another every time?
Anyway, my problem remains. The only things I've been able to see
noticeable changes for are gedit.c and gedit-debug.c. I want to work in
gedit-commands-search.c, but I can't get anything to show noticeable
changes. For example, I change line 142 to make it show "%s no found"
instead of "%s not found" when one searches and finds something wrong,
simply so I can see something different. I run "make;make install" and
it appears to compile and update the proper files, but when I test it
nothing has changed! I've done similar experiments where I remove the
interiors of functions. They compile, generally give me warnings, and
when I run tests on the executable everything seems unmoved by what I
thought were drastic changes.
On 8/12/2010 4:38 PM, Nacho wrote:
Hi Larry,
Some tips to build gedit:
./configure --prefix=your_prefix --libdir=your_libdir
if you are working with the git version try ./autogen.sh instead
of ./configure
then you have to do: make
and after that make install or sudo make install if your prefix
needs root access.
Regards.
On Thu, Aug 12, 2010 at 10:35 PM, Larry
Price <larry.price.ml@gmail.com>
wrote:
I'm
new to open-source programming, and I'm still an amateur at using make.
I'm running into problems while trying to edit code. Whenever I edit
gedit.c, I can see my changes reflected in the executable after I type
"make." Other than that, my modifications don't do anything except for
compile. Is there another command I should be using that's not "make"
when I'm modifying code? I've been trying to edit
"gedit-commands-search.c," but to no avail. Any pointers will be
greatly appreciated. I'm using version 2.30.3.
_______________________________________________
gedit-list mailing list
gedit-list gnome org
http://mail.gnome.org/mailman/listinfo/gedit-list
|
