On Sun, 25 Nov 2012 13:31:32 -0500, Tomek Kott
wrote:
>You might want to take a look at the work done for SharpFossil:
http://repository.mobile-developers.de/cgi-bin/ikoch/sharpfossil/index
>Although it hasn't been worked on in a while, I think some of the commands
>you are looking for have been
On Mon, Nov 26, 2012 at 3:28 PM, Jan Danielsson
wrote:
>
>When I downloaded the win32 fossil binary and installed it on a
> 64-bit windows, I noticed that the fossil ui won't work properly due to
> that it fails to launch new processes. Running command line fossil
> works, but starting new fos
On 11/26/12 21:06, Richard Hipp wrote:
>> fossil uses fork() quite enough, and its memory management depends on
>> that, for
>> what I understand.
>
> The "fossil ui" and "fossil server" commands use fork() on unix. But
> fork() is not available on windows so we have the winhttp.c source file to
On Mon, Nov 26, 2012 at 2:59 PM, Lluís Batlle i Rossell wrote:
>
> fossil uses fork() quite enough, and its memory management depends on
> that, for
> what I understand.
>
The "fossil ui" and "fossil server" commands use fork() on unix. But
fork() is not available on windows so we have the winht
On Mon, Nov 26, 2012 at 01:52:53PM -0600, Nico Williams wrote:
> IIUC the main reason to want a DLL instead of having to spawn a new
> process for every operation is iOS. I hear that the dearth of
> excellent git (and other) SCM clients for iOS has to do with the
> constrained nature of the run-ti
IIUC the main reason to want a DLL instead of having to spawn a new
process for every operation is iOS. I hear that the dearth of
excellent git (and other) SCM clients for iOS has to do with the
constrained nature of the run-time environment.
___
fossil-
by C# programs.
Tomek
> To: fossil-users@lists.fossil-scm.org
> From: gilles.gana...@free.fr
> Date: Sat, 24 Nov 2012 22:40:11 +0100
> Subject: Re: [fossil-users] Fossil as DLL?
>
> On Sat, 24 Nov 2012 15:31:41 -0500, Richard Hipp
> wrote:
> >The current Fossil imple
On Sat, 24 Nov 2012 15:31:41 -0500, Richard Hipp
wrote:
>The current Fossil implementation is not appropriate for converting into a
>library due to its extensive using of global variables and due to a
>cavalier attitude toward freeing allocated memory. Fossil is designed to
>run a single operatio
On Sat, Nov 24, 2012 at 3:20 PM, Gilles wrote:
> Hello
>
> Unless there's a way to call fossil.exe and know how the command
> ended...
>
> http://imageshack.us/photo/my-images/688/fossilprompt.jpg
>
> ... is there a way to recompile the Fossil source code to turn it into
> a DLL* to get
Hello
Unless there's a way to call fossil.exe and know how the command
ended...
http://imageshack.us/photo/my-images/688/fossilprompt.jpg
... is there a way to recompile the Fossil source code to turn it into
a DLL* to get some feedback when calling Fossil programmatically?
Since SQLit
10 matches
Mail list logo