Re: opensync plugin adding todo support

On Wed, Apr 30, 2008 at 12:27:18PM -0700, Paul Eden wrote:
> Thanks!  This will help a lot.

Hi Paul,

I noticed that while we have calendar builder support, it is lacking
in btool, and in testing there are some bugs I've come across today.

This is just a heads-up, in case you're working on Tasks Builder support
and using Calendar as a guide, to do a CVS update every so often
as I'm working on fixing Calendar today.

- Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: opensync plugin adding todo support

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Barry-devel mailing list
Barry-devel@...
https://lists.sourceforge.net/lists/listinfo/barry-devel

Fwd: 64 bit support for Barry

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Barry-devel mailing list
Barry-devel@...
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: Fwd: 64 bit support for Barry

On Thu, May 01, 2008 at 09:34:57PM -0400, Duncan Mak wrote:
> It wouldn't even build.
> 
> Making all in src
> make[3]: Entering directory `/home/duncan/tmp/barry/barry-0.12/src'
> make[3]: *** No rule to make target `all'.  Stop.
> make[3]: Leaving directory `/home/duncan/tmp/barry/barry-0.12/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/duncan/tmp/barry/barry-0.12'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/duncan/tmp/barry/barry-0.12'
> make: *** [debian/stamp-makefile-build] Error 2

Hi Duncan,

Thanks for the config.log.  I looked through it, and couldn't see
too much wrong, except that it is is not generating the makefiles
in the subdirectories tools/ src/ examples/ and man/.

I'm not sure what would cause this.  Check that a new Makefile exists
in each of the above directories before running "make".

If you have autoconf, automake, and libtool installed on your system,
you might try building your own configure, by running "./buildgen.sh cleanall"
then "./buildgen.sh" in the root directory of the Barry sources.

The configure script depends on tools/Makefile.in, src/Makefile.in,
examples/Makefile.in, and man/Makefile.in existing before you run it.
You might check to make sure nothing funky happened during expanding
the tarball.

- Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: Fwd: 64 bit support for Barry

Hi Duncan,

How are you starting the build?

I use the command debuild, from the devscripts package, but you can also
use dpkg-buildpackage from the dpkg-dev package.

Debuild generates everything I need for package I intend to upload.

Either of these should check that you have the dependencies necessary to
build the package.

Also I recently submitted a patch to add some missing
build-dependencies.

--- debian/control      12 Oct 2007 22:32:42 -0000      1.7
+++ debian/control      29 Apr 2008 07:29:13 -0000
 <at>  <at>  -2,7 +2,7  <at>  <at> 
 Section: misc
 Priority: optional
 Maintainer: Chris Frey <cdfrey@...>
-Build-Depends: debhelper (>= 4.0.0), cdbs, pkg-config, libusb-dev,
libssl-dev, libboost-serialization-dev, libtar-dev, libgtkmm-2.4-dev,
libglademm-2.4-dev, libopensync0 (>= 0.22), libopensync0 (<< 0.30)
+Build-Depends: debhelper (>= 4.0.0), cdbs, autoconf, automake, libtool,
pkg-config, libusb-dev, libssl-dev, libboost-serialization-dev,
libtar-dev, libgtkmm-2.4-dev, libglademm-2.4-dev, libopensync0-dev (>=
0.22), libopensync0-dev (<< 0.30)
 Standards-Version: 3.6.1

On Thu, 2008-05-01 at 21:34 -0400, Duncan Mak wrote:
> Hello Chris,
> 
> On Thu, May 1, 2008 at 12:20 PM, Chris Frey <cdfrey@...>
> wrote:
> 
>         On Thu, May 01, 2008 at 04:53:13AM -0400, Duncan Mak wrote:
>         > I just tried building the new barry release, using the
>         Debian source package
>         > files, it seems to fail here:
>         >
>         > checking whether byte ordering is bigendian... no
>         >
>         > Is that a necessary check? Is there a way to run Barry on my
>         64 bit machine?
>         
>         
>         Barry should run on 64 bit.  I just don't have a machine like
>         that handy,
>         so I need folks like you to report bugs. 
>         
>         How does it fail?  Does it stop there, or does Barry just not
>         run
>         properly once compiled?
> 
> It wouldn't even build.
> 
> Making all in src
> make[3]: Entering directory `/home/duncan/tmp/barry/barry-0.12/src'
> make[3]: *** No rule to make target `all'.  Stop.
> make[3]: Leaving directory `/home/duncan/tmp/barry/barry-0.12/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/duncan/tmp/barry/barry-0.12'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/duncan/tmp/barry/barry-0.12'
> make: *** [debian/stamp-makefile-build] Error 2 
> 
>  
> 
>         It is a necessary check, since the Blackberry itself uses
>         little endian
>         data structures.
>         
>         Could you send me your config.log file?
> 
> See attachment.
> 
> 
> -- 
> Duncan. 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________ Barry-devel mailing list
Barry-devel@... https://lists.sourceforge.net/lists/listinfo/barry-devel
--

-- 
Jason Thomas

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: Fwd: 64 bit support for Barry

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Barry-devel mailing list
Barry-devel@...
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: Fwd: 64 bit support for Barry

On Fri, May 02, 2008 at 04:10:12PM -0400, Duncan Mak wrote:
> However, now I'm having problems building the 'gui' directory. Am I missing
> another dependency?

Depends on the error you're getting. 

The dependencies for the GUI build are listed (for now) at:

	http://netdirect.ca/software/packages/barry/install.php

	gtkmm 2.4 - C++ GTK+ wrapper library
	glademm 2.4 - C++ glade wrapper library
	glibmm 2.4 - C++ glib wrapper library
	libtar 1.2.x - TAR file library
	zlib - compression library
	libbarry itself

- Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: Fwd: 64 bit support for Barry

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Barry-devel mailing list
Barry-devel@...
https://lists.sourceforge.net/lists/listinfo/barry-devel

Barry source code repositories

Hi folks,

This will be of interest to developers.  For users, even those tracking
CVS, nothing will change, and you can continue life as always.

I've been using git to manage Barry's source code for the last few weeks
now, and I'm very happy with it.  The observant of you may have noticed
a slight change in the formatting of the CVS log entries, and that's just
because I'm doing it the way git recommends now.

My current work flow is a matter of working in a local git tree, committing
changes and testing work, and once I'm happy with the results, I run a
script which pushes all these changes in patch form to various backup
repositories.  One of these repositories is the Sourceforge CVS tree.

Since it is so easy to push to other repositories in git, there's no reason
not to provide a git tree for developers as well.  This has been done,
and you can find the information here:

	http://repo.or.cz/w/barry.git

That is the web view of the git repository.  If you wish to use it
on your local machine, do something like this:

	git clone git://repo.or.cz/barry.git barry

Submitting changes can happen in one of three methods:

	1) Send a patch to the mailing list or directly to me.  This works
		whether you're using CVS or tarball or git or anything.

	2) Publish your own git repository (perhaps on repo.or.cz itself)
		and tell me to pull from one of your branches when
		you're ready.

	3) Use the "mob" branch.

That last option needs some explanation.

When registering the Barry project on repo.or.cz, there was an interesting
feature available there, which allows anyone to push to a "mob" branch of
a repository, if so configured.

It would go something like this:

	# clone with mob user
	git clone git+ssh://mob@.../srv/git/barry.git barry

	cd barry
	git checkout -b mob origin/mob
	git diff origin/master..mob		# make sure master == mob
	<make changes>
	git add ... && git commit
	git push origin mob
	<send email to the list, include the SHA1 sum of the commit>

This is a novel idea, as well as a security risk for anyone who blindly
runs whatever is in the mob branch.  Hence the recommended diff check
above, to make sure you're running something from me.

The mob user can only push to the mob branch, so all other branches are mine,
and have gone through my own personal checks.  But it frees people up
to use git, who may not have their own hosting, or who may not want to
bother setting up their own git repo.  People can use it to collaborate
on a feature as well.  Let your imagination run wild.

You can read more about it here: http://repo.or.cz/mob.html

One final note: the CVS tree is not going away, and it will contain
the same code as git's master branch does.  If you're comfortable with your
current process, there's no need to change.

As usual, if you have any questions, please ask.

- Chris

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

Re: Fwd: 64 bit support for Barry

On Fri, May 02, 2008 at 08:46:59PM -0400, Duncan Mak wrote:
> configure is not running in the 'gui' directory, so it's not being
> configured and can't be built when make descends into that directory.
> 
> I have all the dependencies satisfied, and I'm building the package using:
> 
>  dpkg-buildpackage -uc -us -rfakeroot

When the build fails from the above command, can you check whether
a barry-0.12/gui/configure file exists?

As a side note, the gui and opensync-plugin directories can be built
in a standalone manner as well.  For example (root not required):

	tar xzf barry-0.12*tar.gz
	cd barry-0.12
	./configure --prefix=/tmp/barry
	make install
	cd gui
	export PKG_CONFIG_PATH=/tmp/barry/lib/pkgconfig
	./configure --prefix=/tmp/barry
	make install
	/tmp/barry/bin/barrybackup

If that works, then we know it is something in the debian package
build process.

- Chris

(Running some tests here, trying to reproduce your issue)

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone