Commit 6cb393f5 authored by Dodji Seketeli's avatar Dodji Seketeli
Browse files

jeudi 22 juin 2006, 16:41:45 (UTC+0200) Dodji Seketeli

        * Initial Import


svn path=/trunk/; revision=4
parents
Rob Page <page.rob@gmail.com>
Dodji Seketeli <dodji@gnome.org>
Large parts of this wrapper (ie: the tools and scripts directories)
are taken from the glibmm and gtkmm projects.
http://www.gtkmm.org
Initial Code by:
Jae Jang <jjang@users.sourceforge.net>
This diff is collapsed.
/AUTHORS/1.1.1.1/Sun May 28 18:56:55 2006//
/COPYING/1.1.1.1/Sun May 28 18:56:55 2006//
/INSTALL/1.1.1.1/Sun May 28 18:56:55 2006//
/MAINTAINERS/1.1.1.1/Sun May 28 18:56:55 2006//
/Makefile.am/1.1.1.1/Sun May 28 18:56:55 2006//
/NEWS/1.1.1.1/Sun May 28 18:56:55 2006//
/README/1.1/Sun May 28 19:00:41 2006//
/README.OLD/1.1.1.1/Sun May 28 18:56:55 2006//
/aclocal.m4/1.1.1.1/Sun May 28 18:56:55 2006//
/autogen.sh/1.1.1.1/Sun May 28 18:56:55 2006//
/configure/1.1.1.1/Sun May 28 18:56:55 2006//
/configure.in/1.1.1.1/Sun May 28 18:56:55 2006//
D/build_shared////
D/gtksourceview////
D/scripts////
D/tools////
/config.h.in/1.1.1.1/Thu Jun 1 18:47:42 2006//
/ChangeLog/1.2/Result of merge+Sun Jun 4 10:54:14 2006//
gtksourceviewmm
:pserver:anonymous@cvs.robpage.co.uk:/var/lib/cvs
samedi 17 juin 2006, 17:16:40 (UTC+0200) Dodji Seketeli <dodji@gnome.org>
* grksourceview/src/*: Added sourcelanguagesmanager.[hg|ccg]. Various
fixes to make the sourceview widget work for various testcases.
* configure.in: put the version number back to 1.0.0 so that we can
expect to keep track with the underlying gtksourceview numbering
scheme.
dimanche 4 juin 2006, 12:34:10 (UTC+0200) Dodji Seketeli <dodji@gnome.org>
* gtksourceview/src/*: added gtksourceview_signals.defs
sourcestylescheme.ccg, sourcestylescheme.hg, sourcetag.ccg,
sourcetag.hg, sourcetagstyle.ccg, sourcetagstyle.hg,
sourcetagtable.ccg, sourcetagtable.hg.
* gtksourceview/src/Makefile.am,Makefile_list_of_hg.am_fragment: changed this to reflect the file
additions.
* gtksourceview/src/gtksourceview.defs: reflect the addition of
gtksourceview_signals.defs. This file is not really used at the
moment. I have generated it with tools/extra_defs_gen/generate_extra_defs.
It seems parts of the generated file cannot be properly parsed by
gmmproc, like some strings delimited by '"' which have the very same
'"' as part of their content, or like the property "no-show-all"
that can not be parse for some obscur reasons. Will look more deeply
into that later. All this gmmproc-foo is still a bit dark to me.
* gtksourceview/src/sourcelanguage.ccg: wrapped
gtk_source_language_get_id(), gtk_source_language_get_tags(),
and gtk_source_language_set_mime_types().
* tools/m4/convert_gtksourceviewmm.m4: updated a couple of conversion
macros.
samedi 3 juin 2006, 09:20:41 (UTC+0200) Dodji Seketeli <dodji@gnome.org>
* gtksourceview/src/sourcelanguage.hg: wrap the set_mime_types()
method.
* tools/m4/convert.m4: include convert_gtkmm.m4 before
convert_gtksourceviewmm.m4 so that the later finds the appropriate
macros definitions.
* tools/m4/convert_gtksourceviewmm.m4: add a couple of m4 conversion
macros needed by gtksourceview/src/*.hg to be properly generated.
This entry makes the tree compile properly compile for me. I haven't
tried to run it yet, though.
2006-05-28 - Rob Page <page.rob@gmail.com>
* Mostly rewritten to use hg and ccg files, but is probably not functional at the moment
2006-04-01 - Rob Page <page.rob@gmail.com>
* Initial Upload.
Index: ChangeLog
===================================================================
RCS file: /var/lib/cvs/gtksourceviewmm/ChangeLog,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 ChangeLog
--- ChangeLog 28 May 2006 18:56:55 -0000 1.1.1.1
+++ ChangeLog 3 Jun 2006 07:33:07 -0000
@@ -1,5 +1,21 @@
+samedi 3 juin 2006, 09:20:41 (UTC+0200) Dodji Seketeli <dodji@gnome.org>
+
+ * gtksourceview/src/sourcelanguage.hg: wrap the set_mime_types()
+ method.
+ * tools/m4/convert.m4: include convert_gtkmm.m4 before
+ convert_gtksourceviewmm.m4 so that the later finds the appropriate
+ macros definitions.
+ * tools/m4/convert_gtksourceviewmm.m4: add a couple of m4 conversion
+ macros needed by gtksourceview/src/*.hg to be properly generated.
+
+ This entry makes the tree compile properly compile for me. I haven't
+ tried to run it yet, though.
+
2006-05-28 - Rob Page <page.rob@gmail.com>
-* Mostly rewritten to use hg and ccg files, but is probably not functional at the moment
+
+ * Mostly rewritten to use hg and ccg files, but is probably not functional at the moment
2006-04-01 - Rob Page <page.rob@gmail.com>
-* Initial Upload.
+
+ * Initial Upload.
+
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
Please use the mailing list (gtkmm-list@gnome.org) instead of emailing developers directly.
Murray Cumming <murrayc@usa.net>
Daniel Elstner <daniel.elstner@gmx.net>
SUBDIRS = tools gtksourceview @EXAMPLE_SUBDIR@ @DEMO_SUBDIR@ tests
DIST_SUBDIRS = $(SUBDIRS) scripts
EXTRA_DIST = build_shared/Makefile_build.am_fragment \
build_shared/Makefile_build_gensrc.am_fragment \
build_shared/Makefile_gensrc.am_fragment \
build_shared/Makefile_conditional.am_fragment \
autogen.sh
all-local:
@echo "*** Everything completed ***"
dist-hook:
@echo; echo; \
echo "**********************************************************"; \
echo "* IMPORTANT NOTICE: *"; \
echo "* *"; \
echo "* Be sure you have done a complete build before running *"; \
echo "* 'make dist' or 'make distcheck', because otherwise *"; \
echo "* the tarball will _not_ contain the dependency rules *"; \
echo "* generated by the compiler. *"; \
echo "**********************************************************"; \
echo; echo
#include $(top_srcdir)/docs/Makefile_web.am_fragment
.PHONY: post-html post-html-local post-html-recursive doc-clean doc-clean-recursive doc-rebuild
This diff is collapsed.
This diff is collapsed.
Readme
This package contains a "gtkmm compliant" wrapper for gtksourceview.
At the moment, it only wraps the widget GtkSourceView into
Gtk::SourceView. The "backend" objects like GtkSourceBuffer,
GtkSourceLanguagesManager etc are still handled through the C interface.
This is not a big problem as the test program will demonstrate.
Gtk::SourceView is a proper decendent of Gtk::TextView and inherits
all the relevant properties and methods. In addition, it adds
methods that wrap gtk_source_view_* functions and handles source view
specific signals.
Other aspects of gtksourceview will be wrapped if there's enough demand.
------------------------------------------------------------------------
Compiling
---------
The configure script doesn't generate a library. You will simply
need to copy three files to your project[see note below]
The included configure script will generate Makefiles to make an example
program called testsourceview in the gtksourceviewmm directory.
Requirements to compile:
gtkmm related libraries (glibmm, sigc++)
gtksourceview 1.1.90 or above (older versions may also work)
libxml2 (required by gtksourceview)
gnomeprint stuff (required by gtksourceview. I chose to remove this
requirement in my gtksourceview installation)
and most importantly:
pkg-config that knows about the libraries listed above.
I have tested with:
gtkmm 2.4.7 glibmm 2.4.5 sigc++ 2.x on linux
gtkmm 2.4.8 glibmm 2.4.x sigc++ 2.x on windows (mingw) with success
Try "pkg-config --list-all" and see if you have all of the above.
If pkg-config doesn't see all the libs, configure script will also
fail to see required libs.
If you think you meet all the dependencies,
./configure
make
(if make succeeds, try out the test app)
cd gtksourceviewmm
./testsourceview
--------------------------------------------------------------------
How to use at the wrapper in your project:
At this time, I chose not to build the wrapper as a separate library and
link in a separate step with the test program, because it's only a
couple of files and it's easier to simply build together with my project.
You can simply copy over sourceview.cpp, sourceview.h, and
private/sourceview_p.h into your project directory and link it in.
Take a look at main.cpp to see an example.
testsourceview is built from main.cpp and sourceview.cpp
This diff is collapsed.
#! /bin/sh
PKG_NAME=gtksourceviewmm
srcdir=`dirname $0`
test "x$srcdir" = x && srcdir=.
origdir=`pwd`
if test -f "$srcdir/configure.in" && \
test -d "$srcdir/gtksourceview/src" && \
test -d "$srcdir/gtksourceview/gtksourceviewmm"
then :; else
echo "** Error **: Directory \`${srcdir}\' does not look like"
echo "the top-level ${PKG_NAME} directory."
exit 1
fi
MAKE=`which gnumake`
test -x "$MAKE" || MAKE=`which gmake`
test -x "$MAKE" || MAKE=`which make`
if "$MAKE" --version 2>/dev/null | grep "Free Software Foundation" >/dev/null 2>&1
then :; else
echo "** Error **: You need GNU make to build gtksourceviewmm from CVS."
echo "${MAKE} is not GNU make."
exit 1
fi
echo "Found GNU make at ${MAKE}... good."
cd "$srcdir"
echo "Adding libtools."
libtoolize --automake || exit 1
echo "Building macros."
aclocal -I "$srcdir/scripts" $ACLOCAL_FLAGS || exit 1
#echo "Building config header."
#autoheader
echo "Building makefiles."
automake --add-missing || exit 1
echo "Building configure."
autoconf || exit 1
enable_warnings=
case "$*" in
*--enable-warnings*|*--disable-warnings*)
;;
*) # enable -Werror by default when building with gcc3
${CXX:-"g++"} --version 2>/dev/null | grep '(GCC) 3\.[0-9]\+\.[0-9]' >/dev/null 2>&1 \
&& enable_warnings='--enable-warnings=hardcore'
;;
esac
cd "$origdir"
rm -f config.cache
if test -z "$AUTOGEN_SUBDIR_MODE"
then
echo "Running $srcdir/configure --enable-maintainer-mode" $enable_warnings "$@"
"$srcdir/configure" --enable-maintainer-mode $enable_warnings "$@" || exit 1
echo
echo 'run "make"'
echo
else
echo
echo 'run "./configure ; make"'
echo
fi
exit 0
/Makefile_build.am_fragment/1.1.1.1/Sun May 28 18:56:55 2006//
/Makefile_build_gensrc.am_fragment/1.1.1.1/Sun May 28 18:56:55 2006//
/Makefile_conditional.am_fragment/1.1.1.1/Sun May 28 18:56:55 2006//
/Makefile_gensrc.am_fragment/1.1.1.1/Sun May 28 18:56:55 2006//
D
gtksourceviewmm/build_shared
:pserver:anonymous@cvs.robpage.co.uk:/var/lib/cvs
## Copyright (c) 2001
## The gtkmm development team.
##
## **** Common rules for inclusion in Makefile.am ****
## Included by Makefile_build_gensrc.am_fragment
##
include $(srcdir)/../src/Makefile_list_of_hg.am_fragment
# Support for DLL on mingw using libtool > 1.4
# When creating DLLs on win32, we need to explicitly add a few extra
# libraries at link time to resolve symbols (remember a dll is like an
# executable).
if PLATFORM_WIN32
no_undefined = -no-undefined -Wl,--export-all-symbols
win32_dlls_extra_libs = $(sublib_win32_dlls_libs)
else
no_undefined =
win32_dlls_extra_libs =
endif
common_ldflags = -version-info $(sublib_libversion) $(no_undefined)
# All modules can include all other modules,
# for instance, so that gdkmm can use headers in pangomm.
all_includes = -I$(top_builddir)/$(sublib_topdir)\
-I$(top_srcdir)/$(sublib_topdir) \
$(sublib_cflags)
dist_sources = $(files_all_built_cc) $(files_all_extra_cc) $(files_all_built_h) $(files_all_extra_h)
DISTFILES = $(DIST_COMMON) $(dist_sources) $(TEXINFOS) $(EXTRA_DIST)
DEFS = @DEFS@ -DG_LOG_DOMAIN=\"$(sublib_name)\"
DEFAULT_INCLUDES =
# DISABLE_DEPRECATED_CFLAGS is empty unless --enable-deprecated is specified to configure:
INCLUDES = $(strip $(all_includes)) $(DISABLE_DEPRECATED_CFLAGS)
sublib_includedir = $(includedir)/$(sublib_libname)/$(sublib_name)
sublib_include_HEADERS = $(files_all_built_h) $(files_all_extra_h)
maintainer-clean-local:
(cd $(srcdir) && rm -f $(files_all_built_cc) $(files_all_built_h))
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment