Re: [fossil-users] Fossil for Android?
On Sat, 26 Feb 2011 20:53:11 -0800 (PST) Timothy Brown javelin...@yahoo.com wrote: For your consideration, How hard would it be to build Fossil for Android? For that matter how hard would it be to get Fossil built for iOS? Since both are Unix variants, it shouldn't be to bad. The makemake script already has two compilers wired in - one for building the build tools, and one for building the cross-compiled binary. That doesn't set TCC in the Makefile, but that's an easy fix. For android, it took about three hours to get it to compile starting from scratch (literally - I had to locate and download the appropriate development kits). The hard part was figuring out the correct thing to set LDFLAGS in the Makefile to for the cross-compilation environment to get a complete link. Doesn't appear to be working very well - but I'm not an android developer, so that's not really surprising. iOS is probably easier - if you're happy using the jailbroken dev tools. Using Apple's tools may be a bit harder. mike -- Mike Meyer m...@mired.org http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil for Android?
Timothy, A very interesting exercise to be sure, but it begs the question: why? i.e. Did you have a particular use in mind? //Bill On 02/27/2011 01:52 PM, Mike Meyer wrote: On Sat, 26 Feb 2011 20:53:11 -0800 (PST) Timothy Brownjavelin...@yahoo.com wrote: For your consideration, How hard would it be to build Fossil for Android? For that matter how hard would it be to get Fossil built for iOS? Since both are Unix variants, it shouldn't be to bad. The makemake script already has two compilers wired in - one for building the build tools, and one for building the cross-compiled binary. That doesn't set TCC in the Makefile, but that's an easy fix. For android, it took about three hours to get it to compile starting from scratch (literally - I had to locate and download the appropriate development kits). The hard part was figuring out the correct thing to set LDFLAGS in the Makefile to for the cross-compilation environment to get a complete link. Doesn't appear to be working very well - but I'm not an android developer, so that's not really surprising. iOS is probably easier - if you're happy using the jailbroken dev tools. Using Apple's tools may be a bit harder. mike ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil for Android?
Bill, I was thinking along the same lines as Steve. Using Fossil to keep track of user changes giving a timeline view of their changes. They wouldn't even know Fossil is there. I could also see taking presentation on an Android Tablet or IPad and being able to access multiple versions to use in presenting from the tablet (which I know a couple of people who take presentations on their IPads now. I remember Richard Hipp uses Fossil to keep all versions of his presentations. He could use software on the IPad to present and make some small changes and update his repository on the IPad then sync when you get home. I could see the same use for Android tablets (even phones) as well. JRuby runs on Android using Ruboto, I could see taking ruby scripts in a repository and potentially using a tablet to edit and deploy them when visiting a location. Of course if I update ruby or any language in the field I don't want those updates not to be part of my repository. Given time many people could come up with other uses for Fossil on iOS and Android. It would also be a feature that I don't of in any other SCM system. Timothy F. Brown ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil for Android?
Hi Mike Would like care to share what you did to get it working (ie. LDFLAGS etc) - I wouldn't mind having a try myself just to see what the process is. Thanks Steve On Mon, Feb 28, 2011 at 4:52 AM, Mike Meyer m...@mired.org wrote: On Sat, 26 Feb 2011 20:53:11 -0800 (PST) Timothy Brown javelin...@yahoo.com wrote: For your consideration, How hard would it be to build Fossil for Android? For that matter how hard would it be to get Fossil built for iOS? Since both are Unix variants, it shouldn't be to bad. The makemake script already has two compilers wired in - one for building the build tools, and one for building the cross-compiled binary. That doesn't set TCC in the Makefile, but that's an easy fix. For android, it took about three hours to get it to compile starting from scratch (literally - I had to locate and download the appropriate development kits). The hard part was figuring out the correct thing to set LDFLAGS in the Makefile to for the cross-compilation environment to get a complete link. Doesn't appear to be working very well - but I'm not an android developer, so that's not really surprising. iOS is probably easier - if you're happy using the jailbroken dev tools. Using Apple's tools may be a bit harder. mike -- Mike Meyer m...@mired.org http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Refactor Engage. Succeed. Repeat. PO Box 802, Labrador, Q 4215, Australia tel: +61 (0)7 5668 3424 web: refactor.com.au ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil for Android?
On Mon, 28 Feb 2011 07:21:58 +1000
Steve Dalton st...@refactor.com.au wrote:
Hi Mike
Would like care to share what you did to get it working (ie. LDFLAGS
etc) - I wouldn't mind having a try myself just to see what the
process is.
Thanks
Steve
Sure.
Note that setting TCC in makemake.tcl doesn't work for builds on
Linux. I believe this is a bug in makemake.tcl, as the value of TCC
gets copied into win/Makefile.mingw properly.
You need to install Googles ndk (that's the Native Developers Kit) for
your platform if you don't have it already. Assuming that's extracted
into $NDK (i.e. $NDK ends in something like android-ndk-r5b), do the
following:
In Makefile in the top level, set:
TCC = arm-eabi-gcc -I$NDK/platforms/android-5/arch-arm/usr/include
LDFLAGS=-Wl,-rpath-link=$NDK/platforms/android-5/arch-arm/usr/lib,-dynamic-linker=/system/bin/linker
-L$NDK/platforms/android-5/arch-arm/usr/lib
-L$NDK/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/lib/gcc/arm-eabi/4.4.0
$NDK/platforms/android-5/arch-arm/usr/lib/crtbegin_dynamic.o -nostdlib -lc
You'll also want to comment out the setting of -DFOSSIL_ENABLE_SSL
and the addition of -lcrypto -lssl to the link line (the ssl libraries
aren't in the ndk).
Two source file tweaks to cover for functionality that isn't included
in the NDK:
Index: src/config.h
===
--- src/config.h
+++ src/config.h
@@ -126,11 +126,11 @@
#endif
/* Unset the following to disable internationalization code. */
#ifndef FOSSIL_I18N
-# define FOSSIL_I18N 1
+// # define FOSSIL_I18N 1
#endif
#if FOSSIL_I18N
# include locale.h
# include langinfo.h
Index: src/user.c
===
--- src/user.c
+++ src/user.c
@@ -86,12 +86,12 @@
/*
** Do a single prompt for a passphrase. Store the results in the blob.
*/
static void prompt_for_passphrase(const char *zPrompt, Blob *pPassphrase){
- char *z = getpass(zPrompt);
- strip_string(pPassphrase, z);
+ //char *z = getpass(zPrompt);
+ //strip_string(pPassphrase, z);
}
/*
** Prompt the user for a password. Store the result in the pPassphrase
** blob.
Given that the NDK is meant to let you write native-mode methods for
Java, but not interact with the user, these being missing make
sense. Obviously, don't do things that might make it prompt for a
password with this fix.
The resulting binary will correctly spit out help text and version
info, but quietly exits or just hang if asked to do any real
work. That might be because I used android-5 instead of whichever
platform was correct for my tablet, but I spent more time getting this
far than I should have (noticed the TCC setting, and just had to see
if it would work out of the box).
mike
--
Mike Meyer m...@mired.org http://www.mired.org/consulting.html
Independent Software developer/SCM consultant, email for more information.
O ascii ribbon campaign - stop html mail - www.asciiribbon.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil on windows-file-server with unc-path
Hello user group, I have an issue with unc pathes on a windows machine. My fossil version is: This is fossil version [6502627a3e] 2011-02-08 12:52:37 UTC Is there any known restraint regarding unc pathes on windows? I tried the following: I had a repo on my harddisk drive C, cloned it to a file server using the unc-path \\server\path\subpath\repo.fossil This worked perfectly. Then I made changes in the local repository and I tried to push these changes into the remote repo on the file server and I get this error message: fossil.exe: server sends error: repository does not exist or is in an unreadable directory: /server/path/subpath/repo.fossil The error message changed backslashes to slashes and skipped one backslash before the server-name. It is possible to start the local server with the remote repo and push the changes using http://127.0.0.1:8080/ but not directly with the file path. Anybody has the same experience? Should it be possible to do this or do I have a comprehension problem? Thank you for any feedback. Regards, Christian -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
