On Mon, Sep 1, 2014 at 9:29 AM, Stephan Beal wrote:
>
> Okay, more git bashing...
>
> {snipped stuff went here}
>
> It occurred to me today that in nearly 31 years of using a computer i
have, in total, lost more data to git (while following the instructions!!!)
than any other single piece of softw
Petr Ferdus wrote:
>
> Thank you Joe for clarifications and your Unix-like system setup recipe.
> I'll try to absorb it and use it.
> Meanwhile it seem that my simple idea of "fossil on windows with embedded
> tcl as a single exe"
> is not that easy as it seems. I have found notes from drh dated
Joe Mistachkin
>No. There are three primary concerns in order to build Fossil with Tcl
>integration enabled and make use of it at runtime:
>
>1. Locating the necessary Tcl header file(s) at compile-time.
>
>Currently, this is handled several different ways, depending on the
>platform. On Unix-li
Petr Ferdus wrote:
>
> Does it mean, that to build "chrooted" version of fossil one must
> omit FOSSIL_TCL_SOURCE (that would be my misundestandin)?
> With unix build, will "chrooted" version containg TCL start-up code?
> (I can't test it)
> Should not the same happen for windows build?
> I would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/1/2014 3:20 AM, Eduardo Morras wrote:
> Can you try to do it "backwards"? (don't know if backwards is the
> rigth word). Create a new repository, import the older source
> files, pull from your repository. Don't sync or your repository
> will bec
Okay, more git bashing...
After losing 3 hours' work today from something as simple as "git stash
save" (where git stashed 3000+ untracked/generated files, despite the docs
saying it doesn't do that), then not being able to do "stash apply"
(because "file already exists..." for 3000+ files), and h
>Datum: 01.09.2014 13:10 Od: Jan Nijtmans
>No, FOSSIL_TCL_SOURCE means that fossil
>expects Tcl to be installed in the indicated directory.
>libtcl8.x.a will be included statically inside fossil,
>but the other files (such as init.tcl) will not be
>part of fossil. To me it is not usefull at all to
Jan Nijtmans
>Whenever I build fossil with Tcl support, I always
>use FOSSIL_ENABLE_TCL=1, FOSSIL_ENABLE_TCL_STUBS = 1,
>FOSSIL_ENABLE_TCL_PRIVATE_STUBS = 1.
Hello Jan,
thank you for the tip.
I would much prefer "static" solution, which would be more in fossil way of one
single executable with
On Sat, 30 Aug 2014 15:03:32 -0500
Andy Goth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 8/30/2014 2:40 PM, Andy Goth wrote:
> > Now I have been given a few older versions. What's the best way to
> > go about putting them into the repository?
> >
> > I know I can check them
2014-09-01 7:58 GMT+02:00 Petr Ferdus :
> I try to compile fossil with FOSSIL_ENABLE_TCL support. Build environment is
> mingw/msys on XP sp3.
> Build is based on fossil 75dcdd0bdb. If I build my version without TCL
> support it works nicely.
>
> When I turn TCL related switches on (FOSSIL_ENABLE
10 matches
Mail list logo
