--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> tl_ocallaghan wrote:
> > I would like to see the Jasspa Source tree moved to Github or similar, and a
contrib tree maintained alongside it.
> >
> > This is for a few reasons:
> >  - Gives everybody the chance to easily follow the mainline
> >  - Allows people to easily maintain their own branch changes against a 
mainline tree or tagged stable release.
> >  - the contrib tree will let people develop, maintain and publish useful
extensions and scripts, without having to dig around the mail archive for them.
> >
> > Jasspa is open source after all, so i should be able to setup a github
account and publish the source myself, but i think it would be better maintained
by the Jasspa people.
> >
> > What do people think?
> >
> > Tim.
> > http://github.com/ is a free for non-commercial use git repository.
> >
>
> Not sure that there have been enough contributions to warrant this. Most of
the
> contributions have been bundled with the release unless we have not understood
> them fully or they are very platform specific and non-portable.
>
> Also I would not want to use GIT because I cannot use it in MicroEmacs -
> probably some motivation to support it I guess but until that point that it is
> supported GIT is certainly not on the menu since we are currently doing most
of
> the work. I think there is a GIT port for Solaris from Jan 2009 this year
> (understand it was a bit of a git to build as well) but certainly not played
> with it yet.
>

It does not need to be integrated as such, SVN or CVS or any source code control
would be ok. The idea is that the contribution level might be improved by a
public source tree. I prefer git because branching and merging is cheap.

Git usage was an assumption on my part because Linus Torvalds uses and maintains
a version of uemacs. It has no git integration either.
http://git.kernel.org/?p=editors/uemacs/uemacs.git;a=summary

Tim.

I have just posted some Intel (x86) Apple binaries to:

http://www.jasspa.com/downapple.html

Many Thanks to Bruno and Steve for arranging and building the binaries,
respectively.

Regards
Jon.

I've just posted an experimental Microsoft Windows me executable to the site
here:

http://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip

The executable includes the macros built-in so it just runs wherever it is and
does not need to be installed so good for a memory stick.

You can actually get to the internal macros tree using the path "bfs://" (bfs
being built-in file system), most likely will change this to "int://" or
"rom://" but at the moment this is simply a prototype. (I know the dates are
incorrect as well).

More interestingly your can run M-x grep in here. You can also copy the whole
tree out using the file browser to copy the directory. Any macros that are
defined outside in the searchable jasspa directories will over-ride the
built-in ones.

Anyway, if you have time then give it a go and see how you like it. I need some
Guinea pigs to test it! Should we ship executables such as this as standard?

Regards
Jon.

Hi Jon
Good work!

I had used standalone application by using StartKits in Tcl and this I would
believe its the same idea concept?

I makes ME (even) more appealing, just one .exe file and your private stuff and
voila :-)

Do you have this concept working for Linux as well ?

Nice work!

Regards,
Pedro

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> I've just posted an experimental Microsoft Windows me executable to the site
here:
>
> http://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip
>
> The executable includes the macros built-in so it just runs wherever it is and
> does not need to be installed so good for a memory stick.
>
> You can actually get to the internal macros tree using the path "bfs://" (bfs
> being built-in file system), most likely will change this to "int://" or
> "rom://" but at the moment this is simply a prototype. (I know the dates are
> incorrect as well).
>
> More interestingly your can run M-x grep in here. You can also copy the whole
> tree out using the file browser to copy the directory. Any macros that are
> defined outside in the searchable jasspa directories will over-ride the
> built-in ones.
>
> Anyway, if you have time then give it a go and see how you like it. I need
some
> Guinea pigs to test it! Should we ship executables such as this as standard?
>
> Regards
> Jon.
>

azynheira wrote:
> Hi Jon
> Good work!
>

Hi Pedro,


> I had used standalone application by using StartKits in Tcl and this I would
believe its the same idea concept?

Yes much the same.

>
> I makes ME (even) more appealing, just one .exe file and your private stuff
and voila :-)

Yes - sometimes you do not want to install but want something a bit more than
nano and just want it to run.

>
> Do you have this concept working for Linux as well ?

I've not built a Linux one yet. Just about to boot up my VMs for Linux testing.
It does work on Sun Solaris so Linux should be the same. I'm just going through
the platforms testing them so I'll post a Linux once I have built and confirmed
its OK.

Regards
Jon.


>
> Nice work!
>
> Regards,
> Pedro
>
> --- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>> I've just posted an experimental Microsoft Windows me executable to the site
here:
>>
>> http://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip
>>
>> The executable includes the macros built-in so it just runs wherever it is
and
>> does not need to be installed so good for a memory stick.
>>
>> You can actually get to the internal macros tree using the path "bfs://" (bfs
>> being built-in file system), most likely will change this to "int://" or
>> "rom://" but at the moment this is simply a prototype. (I know the dates are
>> incorrect as well).
>>
>> More interestingly your can run M-x grep in here. You can also copy the whole
>> tree out using the file browser to copy the directory. Any macros that are
>> defined outside in the searchable jasspa directories will over-ride the
>> built-in ones.
>>
>> Anyway, if you have time then give it a go and see how you like it. I need
some
>> Guinea pigs to test it! Should we ship executables such as this as standard?
>>
>> Regards
>> Jon.
>>
>
>
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
>     mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
>

 

I've just posted an experimental Microsoft Windows me executable to the site here:

http://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip

The executable includes the macros built-in so it just runs wherever it is and
does not need to be installed so good for a memory stick.

You can actually get to the internal macros tree using the path "bfs://" (bfs
being built-in file system), most likely will change this to "int://" or
"rom://" but at the moment this is simply a prototype. (I know the dates are
incorrect as well).

More interestingly your can run M-x grep in here. You can also copy the whole
tree out using the file browser to copy the directory. Any macros that are
defined outside in the searchable jasspa directories will over-ride the
built-in ones.

Anyway, if you have time then give it a go and see how you like it. I need some
Guinea pigs to test it! Should we ship executables such as this as standard?

Regards
Jon.

Bryan Schofield wrote:
>
>
> Brilliant! It would be super brilliant if I could package my JASSPA_HOME
> the same way and bring it along as a single file.

You will be able to do this as well if you roll your own binary.

My built-in file system builder is not quite ready for release yet and only
works on Solaris so I need to port that to other platforms first and tidy it
up. Once I have done this then I'll release it and you will be able to stuff it
as you want. The builder simply recurses a directory tree and compresses and
packs the files and directories into a file system and spits out a 'C' unsigned
char array which is then compiled into the program. You can put what you want
in there with as many directories as you want.

Still checking running on different platforms at the moment.

Regards
Jon.

>
> On Oct 31, 2009, at 5:11 PM, Jon Green <jon@...
> <mailto:jon@...>> wrote:
>
>>
>>
>> I've just posted an experimental Microsoft Windows me executable to
>> the site here:
>>
>>
<http://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip>ht\
tp://www.jasspa.com/development/jasspa-me-standalone-ms-win32-20091017.zip
>>
>> The executable includes the macros built-in so it just runs wherever
>> it is and
>> does not need to be installed so good for a memory stick.
>>
>> You can actually get to the internal macros tree using the path
>> "bfs://" (bfs
>> being built-in file system), most likely will change this to "int://" or
>> "rom://" but at the moment this is simply a prototype. (I know the
>> dates are
>> incorrect as well).
>>
>> More interestingly your can run M-x grep in here. You can also copy
>> the whole
>> tree out using the file browser to copy the directory. Any macros that
>> are
>> defined outside in the searchable jasspa directories will over-ride the
>> built-in ones.
>>
>> Anyway, if you have time then give it a go and see how you like it. I
>> need some
>> Guinea pigs to test it! Should we ship executables such as this as
>> standard?
>>
>> Regards
>> Jon.
>>
>
>
>

azynheira wrote:
> Hi Jon
> Good work!
>
> I had used standalone application by using StartKits in Tcl and this I would
believe its the same idea concept?
>
> I makes ME (even) more appealing, just one .exe file and your private stuff
and voila :-)
>
> Do you have this concept working for Linux as well ?
>

There are some Linux versions amongst others here:

http://www.jasspa.com/development/me-standalone/

Regards
Jon

Hi Jon,
Been playing with it! Looks nice .... :P

Two points worth discussing:
1) I would see this stuff completely integrated into the "regular" build
environment (I believe it's ongoing from the code I saw).

2) Would be nice to have a system wide variable or a bit in the $system variable
(Readonly) to indicate that the executable being ran is a standalone binary.

Comments appreciated...

Regards,
Pedro



--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> azynheira wrote:
> > Hi Jon
> > Good work!
> >
> > I had used standalone application by using StartKits in Tcl and this I would
believe its the same idea concept?
> >
> > I makes ME (even) more appealing, just one .exe file and your private stuff
and voila :-)
> >
> > Do you have this concept working for Linux as well ?
> >
>
> There are some Linux versions amongst others here:
>
> http://www.jasspa.com/development/me-standalone/
>
> Regards
> Jon
>

On Mon 02/11/09 11:59 AM , "azynheira" pedro.gomes@... sent:
> Hi Jon,
> Been playing with it! Looks nice .... :P
>
> Two points worth discussing:
> 1) I would see this stuff completely integrated into the
> "regular" build environment (I believe it's ongoing from the code
> I saw).

It is just a prototype at the moment - the source is not even archived.
There are makefiles updated for Linux/Freebsd/Darwin etc. Build as:

build -t scw
build -t sc

I did provide the source bundle.

> 2) Would be nice to have a system wide variable or a bit in the $system
> variable (Readonly) to indicate that the executable being ran is a
> standalone binary.
> Comments appreciated...

I think that you should be able to do a @stat command on "bfs://" to test if it
is present.
Not tried this or even considered yet - possibly this will not work - that is
why it is alpha.

Regards
Jon.


>
> Regards,
> Pedro
>
>
>
> --- In jasspa
> @yahoogroups.com, Jon Green <jon@...> wrote:>
> > azynheira wrote:
> > > Hi Jon
> > > Good work!
> > >
> > > I had used standalone application by using
> StartKits in Tcl and this I would believe its the same idea
> concept?> >
> > > I makes ME (even) more appealing, just one
> .exe file and your private stuff and voila :-)> >
> > > Do you have this concept working for Linux
> as well ?> >
> >
> > There are some Linux versions amongst others
> here:>
> >
> http://www.jasspa.com/development/me-standalone/>
> > Regards
> > Jon
> >
>
>
>
>
> ------------------------------------
>
> __________________________________________________________________________
> This is an unmoderated list, but new members are moderated to ensure that
> there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
>
> To un-subscribe, send a mail message to
>
> jasspa-unsubscribe@yahoogroups.com
> or visit http://groups.yahoo.com/group/jasspa andmodify your account settings
manually.
>
>
> Yahoo! Groups Links
>
> Individual Email | Traditional
>
> jasspa-unsubscribe@yahoogroups.com
>
>
---- Message sent via KC WebMail - http://webmail.mistral.net/

Hi Jon,
Just some thoughts on the Win32 version:
1) I maybe trying to be perfectionist, but do you think that it could also be a
good approach to put the bfs into a resource reference. This way one could
replace it as wish.

2) Another approach would be to append the bfs to the end of the executable and
at run time the executable would search for the bfs at as trailing information
append to the end of the exe file and load it.
This way it would also allow some flexible plug&play bfs. If nothing was found,
then it would be regular stripped me32.exe.

What do you think about this?

Regards,
Pedro



--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
>
>
>
>  On Mon 02/11/09 11:59 AM , "azynheira" pedro.gomes@... sent:
> > Hi Jon,
> > Been playing with it! Looks nice .... :P
> >
> > Two points worth discussing:
> > 1) I would see this stuff completely integrated into the
> > "regular" build environment (I believe it's ongoing from the code
> > I saw).
>
> It is just a prototype at the moment - the source is not even archived.
> There are makefiles updated for Linux/Freebsd/Darwin etc. Build as:
>
> build -t scw
> build -t sc
>
> I did provide the source bundle.
>
> > 2) Would be nice to have a system wide variable or a bit in the $system
> > variable (Readonly) to indicate that the executable being ran is a
> > standalone binary.
> > Comments appreciated...
>
> I think that you should be able to do a @stat command on "bfs://" to test if
it is present.
> Not tried this or even considered yet - possibly this will not work - that is
why it is alpha.
>
> Regards
> Jon.
>
>
> >
> > Regards,
> > Pedro
> >
> >
> >
> > --- In jasspa
> > @yahoogroups.com, Jon Green <jon@> wrote:>
> > > azynheira wrote:
> > > > Hi Jon
> > > > Good work!
> > > >
> > > > I had used standalone application by using
> > StartKits in Tcl and this I would believe its the same idea
> > concept?> >
> > > > I makes ME (even) more appealing, just one
> > .exe file and your private stuff and voila :-)> >
> > > > Do you have this concept working for Linux
> > as well ?> >
> > >
> > > There are some Linux versions amongst others
> > here:>
> > >
> > http://www.jasspa.com/development/me-standalone/>
> > > Regards
> > > Jon
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > __________________________________________________________________________
> > This is an unmoderated list, but new members are moderated to ensure that
> > there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
> >
> > To un-subscribe, send a mail message to
> >
> > jasspa-unsubscribe@yahoogroups.com
> > or visit http://groups.yahoo.com/group/jasspa andmodify your account
settings manually.
> >
> >
> > Yahoo! Groups Links
> >
> > Individual Email | Traditional
> >
> > jasspa-unsubscribe@yahoogroups.com
> >
> >
> ---- Message sent via KC WebMail - http://webmail.mistral.net/
>

azynheira wrote:
> Hi Jon, Just some thoughts on the Win32 version: 1) I maybe trying to be
> perfectionist, but do you think that it could also be a good approach to put
> the bfs into a resource reference. This way one could replace it as wish.
>
> 2) Another approach would be to append the bfs to the end of the executable
> and at run time the executable would search for the bfs at as trailing
> information append to the end of the exe file and load it. This way it would
> also allow some flexible plug&play bfs. If nothing was found, then it would
> be regular stripped me32.exe.
>

Well done Pedro - top marks; this is exactly what we should do.

This means that we do not need to do a build to change the macros and any Joe
can easily customize. Also the executable is standard, if there is anything on
the end then you can run it, if it is missing then run as normal. Also the
stuff on the end can be huge i.e. spelling dictionaries, the works! This also
satisfies Bryan's requirements of being able to load up with his own private
files.

  From what I have at the moment to this is just a little step - a small tweak
to the container format will mean I can access it from the bottom of the file
to find the root node entry point and then I have the root directory.

Well done - exactly why I alpha'ed it and what I should have thought of - guess
I was not thinking that far ahead just to proof of concept.

Thanks, I will pursue this path as the next revision.

Regards
Jon

> What do you think about this?
>
> Regards, Pedro
>
>

Hi Jon,
Nice ! :P

One thing I forgot to refer yesterday was that it would be nice that the
container is protected against corruption by appending to the beginning headers
of the container some md5sum of the whole "cake", that would then be checked at
startup just to be sure that we dont have "bad" contents inside.

Just some more cents ... :-)

Pedro

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> azynheira wrote:
> > Hi Jon, Just some thoughts on the Win32 version: 1) I maybe trying to be
> > perfectionist, but do you think that it could also be a good approach to put
> > the bfs into a resource reference. This way one could replace it as wish.
> >
> > 2) Another approach would be to append the bfs to the end of the executable
> > and at run time the executable would search for the bfs at as trailing
> > information append to the end of the exe file and load it. This way it would
> > also allow some flexible plug&play bfs. If nothing was found, then it would
> > be regular stripped me32.exe.
> >
>
> Well done Pedro - top marks; this is exactly what we should do.
>
> This means that we do not need to do a build to change the macros and any Joe
> can easily customize. Also the executable is standard, if there is anything on
> the end then you can run it, if it is missing then run as normal. Also the
> stuff on the end can be huge i.e. spelling dictionaries, the works! This also
> satisfies Bryan's requirements of being able to load up with his own private
files.
>
>  From what I have at the moment to this is just a little step - a small tweak
> to the container format will mean I can access it from the bottom of the file
> to find the root node entry point and then I have the root directory.
>
> Well done - exactly why I alpha'ed it and what I should have thought of -
guess
> I was not thinking that far ahead just to proof of concept.
>
> Thanks, I will pursue this path as the next revision.
>
> Regards
> Jon
>
> > What do you think about this?
> >
> > Regards, Pedro
> >
> >
>

I have just posted a new version of me-standalone for some more alpha testing.

This version is concatenated on the bottom of the executable using a command
line utility called "bfs" as follows:

    To build a bfs  archive  then simply  unpack the "metree" and remove  things
    that you do not want in the archive:

    % tar zxvf jasspa-metree-20091017.tar.gz
    % rm -rf ./jasspa/pixmaps

    Build the archive and add to the executable from a directory:

    % bfs -a mypath/mecw -o me ./jasspa

    Append an already existing archive to the executable:

    % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs

    This  should now be a stand alone  executable.  If you append  again it will
    remove the old archive and add a new one. You can list the archive  attached
    to the executable:

    % bfs -l me

    You can remove the archive attached to the executable:

    % bfs -s me

    You can extract the archive  attached to the  executable  which will extract
    the directory tree in the archive to a new directory called "oldarch".

    % bfs -x oldarch me

So you can now build your own attachable and then add to the bottom. If you do
not attach then "me" runs as normal.

The code is NOT ported to windows yet but should work for most versions of
*NIX. I have only tested this on Linux and Solaris so far.

The bfs on a 64-bit build is a bit funny, it allows:

% bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs

but does not allow

% bfs -a me jasspa-metree-20091117.bfs

which it should do. That is the only issue I have found so far.

Have fun!

Regards
Jon.

Jon Green wrote:
> I have just posted a new version of me-standalone for some more alpha testing.
>
> This version is concatenated on the bottom of the executable using a command
> line utility called "bfs" as follows:
>
>    To build a bfs  archive  then simply  unpack the "metree" and remove 
things
>    that you do not want in the archive:
>
>    % tar zxvf jasspa-metree-20091017.tar.gz
>    % rm -rf ./jasspa/pixmaps
>
>    Build the archive and add to the executable from a directory:
>
>    % bfs -a mypath/mecw -o me ./jasspa
>
>    Append an already existing archive to the executable:
>
>    % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
>
>    This  should now be a stand alone  executable.  If you append  again it
will
>    remove the old archive and add a new one. You can list the archive 
attached
>    to the executable:
>
>    % bfs -l me
>
>    You can remove the archive attached to the executable:
>
>    % bfs -s me
>
>    You can extract the archive  attached to the  executable  which will
extract
>    the directory tree in the archive to a new directory called "oldarch".
>
>    % bfs -x oldarch me
>
> So you can now build your own attachable and then add to the bottom. If you do
> not attach then "me" runs as normal.
>
> The code is NOT ported to windows yet but should work for most versions of
> *NIX. I have only tested this on Linux and Solaris so far.
>
> The bfs on a 64-bit build is a bit funny, it allows:
>
> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
>
> but does not allow
>
> % bfs -a me jasspa-metree-20091117.bfs
>
> which it should do. That is the only issue I have found so far.
>
> Have fun!
>

Here is a fix for the amd64 issue I highlighted above.


cd /home/jon/medev/bfs-v0.1.2/
gdiff --context --minimal --ignore-space-change --recursive
"/home/jon/medev/bfs-v0.1.2/ucopy.c~" "/home/jon/medev/bfs-v0.1.2/ucopy.c"

*** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 22:18:07.714444000 +0000
--- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 22:19:37.927169000 +0000
***************
*** 145,151 ****
    int
    bfs_fileappend (int options, char *srcfile, char *destfile)
    {
!     int status;
        FILE *rfp;
        FILE *wfp;

--- 145,151 ----
    int
    bfs_fileappend (int options, char *srcfile, char *destfile)
    {
!     int status = 0;
        FILE *rfp;
        FILE *wfp;

[EXIT 1]

Jon.

Hi Jon,
Looks nice, I'm giving it a try the next few days ... :P

Do you mind if I do the Win32 port of the stuff ?

Regards,
Pedro

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> Jon Green wrote:
> > I have just posted a new version of me-standalone for some more alpha
testing.
> >
> > This version is concatenated on the bottom of the executable using a command
> > line utility called "bfs" as follows:
> >
> >    To build a bfs  archive  then simply  unpack the "metree" and remove 
things
> >    that you do not want in the archive:
> >
> >    % tar zxvf jasspa-metree-20091017.tar.gz
> >    % rm -rf ./jasspa/pixmaps
> >
> >    Build the archive and add to the executable from a directory:
> >
> >    % bfs -a mypath/mecw -o me ./jasspa
> >
> >    Append an already existing archive to the executable:
> >
> >    % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >
> >    This  should now be a stand alone  executable.  If you append  again it
will
> >    remove the old archive and add a new one. You can list the archive 
attached
> >    to the executable:
> >
> >    % bfs -l me
> >
> >    You can remove the archive attached to the executable:
> >
> >    % bfs -s me
> >
> >    You can extract the archive  attached to the  executable  which will
extract
> >    the directory tree in the archive to a new directory called "oldarch".
> >
> >    % bfs -x oldarch me
> >
> > So you can now build your own attachable and then add to the bottom. If you
do
> > not attach then "me" runs as normal.
> >
> > The code is NOT ported to windows yet but should work for most versions of
> > *NIX. I have only tested this on Linux and Solaris so far.
> >
> > The bfs on a 64-bit build is a bit funny, it allows:
> >
> > % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >
> > but does not allow
> >
> > % bfs -a me jasspa-metree-20091117.bfs
> >
> > which it should do. That is the only issue I have found so far.
> >
> > Have fun!
> >
>
> Here is a fix for the amd64 issue I highlighted above.
>
>
> cd /home/jon/medev/bfs-v0.1.2/
> gdiff --context --minimal --ignore-space-change --recursive
> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" "/home/jon/medev/bfs-v0.1.2/ucopy.c"
>
> *** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 22:18:07.714444000 +0000
> --- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 22:19:37.927169000 +0000
> ***************
> *** 145,151 ****
>    int
>    bfs_fileappend (int options, char *srcfile, char *destfile)
>    {
> !     int status;
>        FILE *rfp;
>        FILE *wfp;
>
> --- 145,151 ----
>    int
>    bfs_fileappend (int options, char *srcfile, char *destfile)
>    {
> !     int status = 0;
>        FILE *rfp;
>        FILE *wfp;
>
> [EXIT 1]
>
> Jon.
>

azynheira wrote:
> Hi Jon,
> Looks nice, I'm giving it a try the next few days ... :P
>
> Do you mind if I do the Win32 port of the stuff ?
>
> Regards,
> Pedro
>

I think it all just about builds on Windows.

I got a bfs.exe building under minGW with virtually no changes to the code last
night. I've not compiled a me32.exe yet but I think this should be fine,
possibly need to define fseeko=>fseek ad ftello=>ftell.

Jon




> --- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>> Jon Green wrote:
>>> I have just posted a new version of me-standalone for some more alpha
testing.
>>>
>>> This version is concatenated on the bottom of the executable using a command
>>> line utility called "bfs" as follows:
>>>
>>>    To build a bfs  archive  then simply  unpack the "metree" and remove 
things
>>>    that you do not want in the archive:
>>>
>>>    % tar zxvf jasspa-metree-20091017.tar.gz
>>>    % rm -rf ./jasspa/pixmaps
>>>
>>>    Build the archive and add to the executable from a directory:
>>>
>>>    % bfs -a mypath/mecw -o me ./jasspa
>>>
>>>    Append an already existing archive to the executable:
>>>
>>>    % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
>>>
>>>    This  should now be a stand alone  executable.  If you append  again it
will
>>>    remove the old archive and add a new one. You can list the archive 
attached
>>>    to the executable:
>>>
>>>    % bfs -l me
>>>
>>>    You can remove the archive attached to the executable:
>>>
>>>    % bfs -s me
>>>
>>>    You can extract the archive  attached to the  executable  which will
extract
>>>    the directory tree in the archive to a new directory called "oldarch".
>>>
>>>    % bfs -x oldarch me
>>>
>>> So you can now build your own attachable and then add to the bottom. If you
do
>>> not attach then "me" runs as normal.
>>>
>>> The code is NOT ported to windows yet but should work for most versions of
>>> *NIX. I have only tested this on Linux and Solaris so far.
>>>
>>> The bfs on a 64-bit build is a bit funny, it allows:
>>>
>>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
>>>
>>> but does not allow
>>>
>>> % bfs -a me jasspa-metree-20091117.bfs
>>>
>>> which it should do. That is the only issue I have found so far.
>>>
>>> Have fun!
>>>
>> Here is a fix for the amd64 issue I highlighted above.
>>
>>
>> cd /home/jon/medev/bfs-v0.1.2/
>> gdiff --context --minimal --ignore-space-change --recursive
>> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" "/home/jon/medev/bfs-v0.1.2/ucopy.c"
>>
>> *** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 22:18:07.714444000 +0000
>> --- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 22:19:37.927169000 +0000
>> ***************
>> *** 145,151 ****
>>    int
>>    bfs_fileappend (int options, char *srcfile, char *destfile)
>>    {
>> !     int status;
>>        FILE *rfp;
>>        FILE *wfp;
>>
>> --- 145,151 ----
>>    int
>>    bfs_fileappend (int options, char *srcfile, char *destfile)
>>    {
>> !     int status = 0;
>>        FILE *rfp;
>>        FILE *wfp;
>>
>> [EXIT 1]
>>
>> Jon.
>>
>
>
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
>     mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
>

Hi Jon,
I patched the makefile and some of the files and was able to produce a bfs.exe
and mew32.exe files to try it out in Win32. The results are the following:

1) No crashes as you predirected! :P

2) I have some problems creating archives (outut below). May be it as to be do
with the endeanness of the thing ....

I'll look into it...

Regards,
Pedro
--- cut here ---
D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a d:\me\pedro.bfs d:\me\pt101224
Stripping archive and none attached "d:\me\pedro.bfs"
Building from directory "d:\me\pt101224"
Archive commencing from byte offset 787040
ERROR: "d:\me\pt101224/attic/Siemens.emf" size mismatch 98!=104
ERROR: "d:\me\pt101224/lsdmengb.edf" size mismatch 342!=470142
ERROR: "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950
ERROR: "d:\me\pt101224/lsdxengb.edf" size mismatch 751!=508084
ERROR: "d:\me\pt101224/old/default.emf" size mismatch 29!=30
ERROR: "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86
ERROR: "d:\me\pt101224/old/pedro.zip" size mismatch 742!=223701
Archive constructed 393520 bytes
Completed archive build from "d:\me\pt101224" [ok]
---cut here --


--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> azynheira wrote:
> > Hi Jon,
> > Looks nice, I'm giving it a try the next few days ... :P
> >
> > Do you mind if I do the Win32 port of the stuff ?
> >
> > Regards,
> > Pedro
> >
>
> I think it all just about builds on Windows.
>
> I got a bfs.exe building under minGW with virtually no changes to the code
last
> night. I've not compiled a me32.exe yet but I think this should be fine,
> possibly need to define fseeko=>fseek ad ftello=>ftell.
>
> Jon
>
>
>
>
> > --- In jasspa@yahoogroups.com, Jon Green <jon@> wrote:
> >> Jon Green wrote:
> >>> I have just posted a new version of me-standalone for some more alpha
testing.
> >>>
> >>> This version is concatenated on the bottom of the executable using a
command
> >>> line utility called "bfs" as follows:
> >>>
> >>>    To build a bfs  archive  then simply  unpack the "metree" and remove 
things
> >>>    that you do not want in the archive:
> >>>
> >>>    % tar zxvf jasspa-metree-20091017.tar.gz
> >>>    % rm -rf ./jasspa/pixmaps
> >>>
> >>>    Build the archive and add to the executable from a directory:
> >>>
> >>>    % bfs -a mypath/mecw -o me ./jasspa
> >>>
> >>>    Append an already existing archive to the executable:
> >>>
> >>>    % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >>>
> >>>    This  should now be a stand alone  executable.  If you append  again it
will
> >>>    remove the old archive and add a new one. You can list the archive 
attached
> >>>    to the executable:
> >>>
> >>>    % bfs -l me
> >>>
> >>>    You can remove the archive attached to the executable:
> >>>
> >>>    % bfs -s me
> >>>
> >>>    You can extract the archive  attached to the  executable  which will
extract
> >>>    the directory tree in the archive to a new directory called "oldarch".
> >>>
> >>>    % bfs -x oldarch me
> >>>
> >>> So you can now build your own attachable and then add to the bottom. If
you do
> >>> not attach then "me" runs as normal.
> >>>
> >>> The code is NOT ported to windows yet but should work for most versions of
> >>> *NIX. I have only tested this on Linux and Solaris so far.
> >>>
> >>> The bfs on a 64-bit build is a bit funny, it allows:
> >>>
> >>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >>>
> >>> but does not allow
> >>>
> >>> % bfs -a me jasspa-metree-20091117.bfs
> >>>
> >>> which it should do. That is the only issue I have found so far.
> >>>
> >>> Have fun!
> >>>
> >> Here is a fix for the amd64 issue I highlighted above.
> >>
> >>
> >> cd /home/jon/medev/bfs-v0.1.2/
> >> gdiff --context --minimal --ignore-space-change --recursive
> >> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" "/home/jon/medev/bfs-v0.1.2/ucopy.c"
> >>
> >> *** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 22:18:07.714444000 +0000
> >> --- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 22:19:37.927169000 +0000
> >> ***************
> >> *** 145,151 ****
> >>    int
> >>    bfs_fileappend (int options, char *srcfile, char *destfile)
> >>    {
> >> !     int status;
> >>        FILE *rfp;
> >>        FILE *wfp;
> >>
> >> --- 145,151 ----
> >>    int
> >>    bfs_fileappend (int options, char *srcfile, char *destfile)
> >>    {
> >> !     int status = 0;
> >>        FILE *rfp;
> >>        FILE *wfp;
> >>
> >> [EXIT 1]
> >>
> >> Jon.
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > __________________________________________________________________________
> >
> > This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> > any material posted to this list.
> >
> > To un-subscribe, send a mail message to
> >
> >     mailto:jasspa-unsubscribe@yahoogroups.com
> >
> > or visit http://groups.yahoo.com/group/jasspa and
> > modify your account settings manually.
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

 

Hi Jon,
I patched the makefile and some of the files and was able to produce a bfs.exe and mew32.exe files to try it out in Win32. The results are the following:

1) No crashes as you predirected! :P

2) I have some problems creating archives (outut below). May be it as to be do with the endeanness of the thing ....

I'll look into it...

Regards,
Pedro
--- cut here ---
D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a d:\me\pedro.bfs d:\me\pt101224
Stripping archive and none attached "d:\me\pedro.bfs"
Building from directory "d:\me\pt101224"
Archive commencing from byte offset 787040
ERROR: "d:\me\pt101224/attic/Siemens.emf" size mismatch 98!=104
ERROR: "d:\me\pt101224/lsdmengb.edf" size mismatch 342!=470142
ERROR: "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950
ERROR: "d:\me\pt101224/lsdxengb.edf" size mismatch 751!=508084
ERROR: "d:\me\pt101224/old/default.emf" size mismatch 29!=30
ERROR: "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86
ERROR: "d:\me\pt101224/old/pedro.zip" size mismatch 742!=223701
Archive constructed 393520 bytes
Completed archive build from "d:\me\pt101224" [ok]
---cut here --

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> azynheira wrote:
> > Hi Jon,
> > Looks nice, I'm giving it a try the next few days ... :P
> >
> > Do you mind if I do the Win32 port of the stuff ?
> >
> > Regards,
> > Pedro
> >
>
> I think it all just about builds on Windows.
>
> I got a bfs.exe building under minGW with virtually no changes to the code last
> night. I've not compiled a me32.exe yet but I think this should be fine,
> possibly need to define fseeko=>fseek ad ftello=>ftell.
>
> Jon
>
>
>
>
> > --- In jasspa@yahoogroups.com, Jon Green <jon@> wrote:
> >> Jon Green wrote:
> >>> I have just posted a new version of me-standalone for some more alpha testing.
> >>>
> >>> This version is concatenated on the bottom of the executable using a command
> >>> line utility called "bfs" as follows:
> >>>
> >>> To build a bfs archive then simply unpack the "metree" and remove things
> >>> that you do not want in the archive:
> >>>
> >>> % tar zxvf jasspa-metree-20091017.tar.gz
> >>> % rm -rf ./jasspa/pixmaps
> >>>
> >>> Build the archive and add to the executable from a directory:
> >>>
> >>> % bfs -a mypath/mecw -o me ./jasspa
> >>>
> >>> Append an already existing archive to the executable:
> >>>
> >>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >>>
> >>> This should now be a stand alone executable. If you append again it will
> >>> remove the old archive and add a new one. You can list the archive attached
> >>> to the executable:
> >>>
> >>> % bfs -l me
> >>>
> >>> You can remove the archive attached to the executable:
> >>>
> >>> % bfs -s me
> >>>
> >>> You can extract the archive attached to the executable which will extract
> >>> the directory tree in the archive to a new directory called "oldarch".
> >>>
> >>> % bfs -x oldarch me
> >>>
> >>> So you can now build your own attachable and then add to the bottom. If you do
> >>> not attach then "me" runs as normal.
> >>>
> >>> The code is NOT ported to windows yet but should work for most versions of
> >>> *NIX. I have only tested this on Linux and Solaris so far.
> >>>
> >>> The bfs on a 64-bit build is a bit funny, it allows:
> >>>
> >>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> >>>
> >>> but does not allow
> >>>
> >>> % bfs -a me jasspa-metree-20091117.bfs
> >>>
> >>> which it should do. That is the only issue I have found so far.
> >>>
> >>> Have fun!
> >>>
> >> Here is a fix for the amd64 issue I highlighted above.
> >>
> >>
> >> cd /home/jon/medev/bfs-v0.1.2/
> >> gdiff --context --minimal --ignore-space-change --recursive
> >> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" "/home/jon/medev/bfs-v0.1.2/ucopy.c"
> >>
> >> *** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 22:18:07.714444000 +0000
> >> --- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 22:19:37.927169000 +0000
> >> ***************
> >> *** 145,151 ****
> >> int
> >> bfs_fileappend (int options, char *srcfile, char *destfile)
> >> {
> >> ! int status;
> >> FILE *rfp;
> >> FILE *wfp;
> >>
> >> --- 145,151 ----
> >> int
> >> bfs_fileappend (int options, char *srcfile, char *destfile)
> >> {
> >> ! int status = 0;
> >> FILE *rfp;
> >> FILE *wfp;
> >>
> >> [EXIT 1]
> >>
> >> Jon.
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > __________________________________________________________
> >
> > This is an unmoderated list, but new members are moderated to ensure that there are no spam users. JASSPA is not responsible for the content of
> > any material posted to this list.
> >
> > To un-subscribe, send a mail message to
> >
> > mailto:jasspa-unsubscribe@yahoogroups.com
> >
> > or visit http://groups.yahoo.com/group/jasspa and
> > modify your account settings manually.
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

Hi All,
Steve, you were right, some replacing of "r" => "rb" and it seems to be working
as if should. The archive is correctly generated now ...

Regards,
Pedro
--- In jasspa@yahoogroups.com, Steven Phillips <bill@...> wrote:
>
> Initial thought is that the bfs program is not opening the files binary
> (i.e. "r" instead of "rb" and "w" instead of "wb") - doesn't make a lot
> of difference on unix but does on windows.
>
> Steve
>
> azynheira wrote:
> >
> >
> > Hi Jon,
> > I patched the makefile and some of the files and was able to produce a
> > bfs.exe and mew32.exe files to try it out in Win32. The results are
> > the following:
> >
> > 1) No crashes as you predirected! :P
> >
> > 2) I have some problems creating archives (outut below). May be it as
> > to be do with the endeanness of the thing ....
> >
> > I'll look into it...
> >
> > Regards,
> > Pedro
> > --- cut here ---
> > D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a d:\me\pedro.bfs d:\me\pt101224
> > Stripping archive and none attached "d:\me\pedro.bfs"
> > Building from directory "d:\me\pt101224"
> > Archive commencing from byte offset 787040
> > ERROR: "d:\me\pt101224/attic/Siemens.emf" size mismatch 98!=104
> > ERROR: "d:\me\pt101224/lsdmengb.edf" size mismatch 342!=470142
> > ERROR: "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950
> > ERROR: "d:\me\pt101224/lsdxengb.edf" size mismatch 751!=508084
> > ERROR: "d:\me\pt101224/old/default.emf" size mismatch 29!=30
> > ERROR: "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86
> > ERROR: "d:\me\pt101224/old/pedro.zip" size mismatch 742!=223701
> > Archive constructed 393520 bytes
> > Completed archive build from "d:\me\pt101224" [ok]
> > ---cut here --
> >
> > --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>, Jon
> > Green <jon@> wrote:
> > >
> > > azynheira wrote:
> > > > Hi Jon,
> > > > Looks nice, I'm giving it a try the next few days ... :P
> > > >
> > > > Do you mind if I do the Win32 port of the stuff ?
> > > >
> > > > Regards,
> > > > Pedro
> > > >
> > >
> > > I think it all just about builds on Windows.
> > >
> > > I got a bfs.exe building under minGW with virtually no changes to
> > the code last
> > > night. I've not compiled a me32.exe yet but I think this should be
> > fine,
> > > possibly need to define fseeko=>fseek ad ftello=>ftell.
> > >
> > > Jon
> > >
> > >
> > >
> > >
> > > > --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>,
> > Jon Green <jon@> wrote:
> > > >> Jon Green wrote:
> > > >>> I have just posted a new version of me-standalone for some more
> > alpha testing.
> > > >>>
> > > >>> This version is concatenated on the bottom of the executable
> > using a command
> > > >>> line utility called "bfs" as follows:
> > > >>>
> > > >>> To build a bfs archive then simply unpack the "metree" and
> > remove things
> > > >>> that you do not want in the archive:
> > > >>>
> > > >>> % tar zxvf jasspa-metree-20091017.tar.gz
> > > >>> % rm -rf ./jasspa/pixmaps
> > > >>>
> > > >>> Build the archive and add to the executable from a directory:
> > > >>>
> > > >>> % bfs -a mypath/mecw -o me ./jasspa
> > > >>>
> > > >>> Append an already existing archive to the executable:
> > > >>>
> > > >>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> > > >>>
> > > >>> This should now be a stand alone executable. If you append again
> > it will
> > > >>> remove the old archive and add a new one. You can list the
> > archive attached
> > > >>> to the executable:
> > > >>>
> > > >>> % bfs -l me
> > > >>>
> > > >>> You can remove the archive attached to the executable:
> > > >>>
> > > >>> % bfs -s me
> > > >>>
> > > >>> You can extract the archive attached to the executable which
> > will extract
> > > >>> the directory tree in the archive to a new directory called
> > "oldarch".
> > > >>>
> > > >>> % bfs -x oldarch me
> > > >>>
> > > >>> So you can now build your own attachable and then add to the
> > bottom. If you do
> > > >>> not attach then "me" runs as normal.
> > > >>>
> > > >>> The code is NOT ported to windows yet but should work for most
> > versions of
> > > >>> *NIX. I have only tested this on Linux and Solaris so far.
> > > >>>
> > > >>> The bfs on a 64-bit build is a bit funny, it allows:
> > > >>>
> > > >>> % bfs -a mypath/mecw -o me jasspa-metree-20091117.bfs
> > > >>>
> > > >>> but does not allow
> > > >>>
> > > >>> % bfs -a me jasspa-metree-20091117.bfs
> > > >>>
> > > >>> which it should do. That is the only issue I have found so far.
> > > >>>
> > > >>> Have fun!
> > > >>>
> > > >> Here is a fix for the amd64 issue I highlighted above.
> > > >>
> > > >>
> > > >> cd /home/jon/medev/bfs-v0.1.2/
> > > >> gdiff --context --minimal --ignore-space-change --recursive
> > > >> "/home/jon/medev/bfs-v0.1.2/ucopy.c~"
> > "/home/jon/medev/bfs-v0.1.2/ucopy.c"
> > > >>
> > > >> *** /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08
> > 22:18:07.714444000 +0000
> > > >> --- /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08
> > 22:19:37.927169000 +0000
> > > >> ***************
> > > >> *** 145,151 ****
> > > >> int
> > > >> bfs_fileappend (int options, char *srcfile, char *destfile)
> > > >> {
> > > >> ! int status;
> > > >> FILE *rfp;
> > > >> FILE *wfp;
> > > >>
> > > >> --- 145,151 ----
> > > >> int
> > > >> bfs_fileappend (int options, char *srcfile, char *destfile)
> > > >> {
> > > >> ! int status = 0;
> > > >> FILE *rfp;
> > > >> FILE *wfp;
> > > >>
> > > >> [EXIT 1]
> > > >>
> > > >> Jon.
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > __________________________________________________________
> > > >
> > > > This is an unmoderated list, but new members are moderated to
> > ensure that there are no spam users. JASSPA is not responsible for the
> > content of
> > > > any material posted to this list.
> > > >
> > > > To un-subscribe, send a mail message to
> > > >
> > > > mailto:jasspa-unsubscribe@yahoogroups.com
> > <mailto:jasspa-unsubscribe%40yahoogroups.com>
> > > >
> > > > or visit http://groups.yahoo.com/group/jasspa
> > <http://groups.yahoo.com/group/jasspa> and
> > > > modify your account settings manually.
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
>

On Mon 09/11/09 12:15 PM , "azynheira" pedro.gomes@... sent:
> Hi All,
> Steve, you were right, some replacing of "r" => "rb"
> and it seems to be working as if should. The archive is correctly generated
> now ...
> Regards,
> Pedro

Hi Pedro,

You are the first on Windows.
Is it working now? Can you build an archive, add it and it runs file in windows?

Jon

> --- In jasspa
> @yahoogroups.com, Steven Phillips <bill@...> wrote:>
> > Initial thought is that the bfs program is not
> opening the files binary > (i.e. "r" instead of "rb"
> and "w" instead of "wb") - doesn't make a lot
> > of difference on unix but does on
> windows.>
> > Steve
> >
> > azynheira wrote:
> > >
> > >
> > > Hi Jon,
> > > I patched the makefile and some of the
> files and was able to produce a > > bfs.exe and mew32.exe files to try it out
> in Win32. The results are > > the following:
> > >
> > > 1) No crashes as you predirected!
> :P> >
> > > 2) I have some problems creating archives
> (outut below). May be it as > > to be do with the endeanness of the thing
> ....> >
> > > I'll look into it...
> > >
> > > Regards,
> > > Pedro
> > > --- cut here ---
> > > D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a
> d:\me\pedro.bfs d:\me\pt101224> > Stripping archive and none attached
> "d:\me\pedro.bfs"> > Building from directory
> "d:\me\pt101224"> > Archive commencing from byte offset
> 787040> > ERROR:
> "d:\me\pt101224/attic/Siemens.emf" size mismatch
> 98!=104> > ERROR:
> "d:\me\pt101224/lsdmengb.edf" size mismatch
> 342!=470142> > ERROR:
> "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950> > ERROR:
> "d:\me\pt101224/lsdxengb.edf" size mismatch
> 751!=508084> > ERROR:
> "d:\me\pt101224/old/default.emf" size mismatch 29!=30> > ERROR:
> "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86> > ERROR:
> "d:\me\pt101224/old/pedro.zip" size mismatch
> 742!=223701> > Archive constructed 393520 bytes
> > > Completed archive build from
> "d:\me\pt101224" [ok]> > ---cut here --
> > >
> > > --- In jasspa
> @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, Jon
> > > Green <jon@> wrote:
> > > >
> > > > azynheira wrote:
> > > > > Hi Jon,
> > > > > Looks nice, I'm giving it a try
> the next few days ... :P> > > >
> > > > > Do you mind if I do the Win32
> port of the stuff ?> > > >
> > > > > Regards,
> > > > > Pedro
> > > > >
> > > >
> > > > I think it all just about builds on
> Windows.> > >
> > > > I got a bfs.exe building under minGW
> with virtually no changes to > > the code last
> > > > night. I've not compiled a me32.exe
> yet but I think this should be > > fine,
> > > > possibly need to define
> fseeko=>fseek ad ftello=>ftell.> > >
> > > > Jon
> > > >
> > > >
> > > >
> > > >
> > > > > --- In jasspa
> @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, > > Jon Green <jon@>
wrote:
> > > > >> Jon Green wrote:
> > > > >>> I have just posted a new
> version of me-standalone for some more > > alpha testing.
> > > > >>>
> > > > >>> This version is
> concatenated on the bottom of the executable > > using a command
> > > > >>> line utility called
> "bfs" as follows:> > > >>>
> > > > >>> To build a bfs archive
> then simply unpack the "metree" and > > remove things
> > > > >>> that you do not want in
> the archive:> > > >>>
> > > > >>> % tar zxvf
> jasspa-metree-20091017.tar.gz> > > >>> % rm -rf
> ./jasspa/pixmaps> > > >>>
> > > > >>> Build the archive and add
> to the executable from a directory:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me ./jasspa> > > >>>
> > > > >>> Append an already
> existing archive to the executable:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me jasspa-metree-20091117.bfs> > > >>>
> > > > >>> This should now be a
> stand alone executable. If you append again > > it will
> > > > >>> remove the old archive
> and add a new one. You can list the > > archive attached
> > > > >>> to the
> executable:> > > >>>
> > > > >>> % bfs -l me
> > > > >>>
> > > > >>> You can remove the
> archive attached to the executable:> > > >>>
> > > > >>> % bfs -s me
> > > > >>>
> > > > >>> You can extract the
> archive attached to the executable which > > will extract
> > > > >>> the directory tree in the
> archive to a new directory called > > "oldarch".
> > > > >>>
> > > > >>> % bfs -x oldarch
> me> > > >>>
> > > > >>> So you can now build your
> own attachable and then add to the > > bottom. If you do
> > > > >>> not attach then
> "me" runs as normal.> > > >>>
> > > > >>> The code is NOT ported to
> windows yet but should work for most > > versions of
> > > > >>> *NIX. I have only tested
> this on Linux and Solaris so far.> > > >>>
> > > > >>> The bfs on a 64-bit build
> is a bit funny, it allows:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me jasspa-metree-20091117.bfs> > > >>>
> > > > >>> but does not
> allow> > > >>>
> > > > >>> % bfs -a me
> jasspa-metree-20091117.bfs> > > >>>
> > > > >>> which it should do. That
> is the only issue I have found so far.> > > >>>
> > > > >>> Have fun!
> > > > >>>
> > > > >> Here is a fix for the amd64
> issue I highlighted above.> > > >>
> > > > >>
> > > > >> cd
> /home/jon/medev/bfs-v0.1.2/> > > >> gdiff --context --minimal
> --ignore-space-change --recursive> > > >>
> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" > >
> "/home/jon/medev/bfs-v0.1.2/ucopy.c"> > > >>
> > > > >> ***
> /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 > > 22:18:07.714444000 +0000
> > > > >> ---
> /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 > > 22:19:37.927169000 +0000
> > > > >> ***************
> > > > >> *** 145,151 ****
> > > > >> int
> > > > >> bfs_fileappend (int options,
> char *srcfile, char *destfile)> > > >> {
> > > > >> ! int status;
> > > > >> FILE *rfp;
> > > > >> FILE *wfp;
> > > > >>
> > > > >> --- 145,151 ----
> > > > >> int
> > > > >> bfs_fileappend (int options,
> char *srcfile, char *destfile)> > > >> {
> > > > >> ! int status = 0;
> > > > >> FILE *rfp;
> > > > >> FILE *wfp;
> > > > >>
> > > > >> [EXIT 1]
> > > > >>
> > > > >> Jon.
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ------------------------------------> > > >
> > > > >
> __________________________________________________________> > > >
> > > > > This is an unmoderated list, but
> new members are moderated to > > ensure that there are no spam users. JASSPA
> is not responsible for the > > content of
> > > > > any material posted to this
> list.> > > >
> > > > > To un-subscribe, send a mail
> message to> > > >
> > > > > jasspa-unsubscribe@yahoogroups.com > >
> <mailto:jasspa-unsubscribe%40yahoogroups.com>> > > >
> > > > > or visit http://groups.yahoo.com/group/jasspa > >
<http://groups.yahoo.com/group/jasspa>
> and> > > > modify your account settings
> manually.> > > >
> > > > >
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> __________________________________________________________________________
> This is an unmoderated list, but new members are moderated to ensure that
> there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
>
> To un-subscribe, send a mail message to
>
> jasspa-unsubscribe@yahoogroups.com
> or visit http://groups.yahoo.com/group/jasspa andmodify your account settings
manually.
>
>
> Yahoo! Groups Links
>
> Individual Email | Traditional
>
> jasspa-unsubscribe@yahoogroups.com
>
>
---- Message sent via KC WebMail - http://webmail.mistral.net/

Hi,
Yes, after Steve's suggestion ITS ALIVE :-) ... (add mad laughter at
will :-))

The archive is built correctly and the integrity is correct (by using
-t), and the .exe file produced does recognize the internal fs if I use
bfs://foobar ... It works correctly!

Production log:
D:\ME\src\std2\bfs-v0.1.1>bfs -a mypath/mecw -o me ./jasspa
Copying "mypath/mecw" => "me"
Error: Cannot access file "mypath/mecw"
Copied "mypath/mecw" => "me" [fail]

D:\ME\src\std2\bfs-v0.1.1>bfs -a ..\src\mew32.exe -o mex d:\ME\metree
Copying "..\src\mew32.exe" => "mex"
Copied "..\src\mew32.exe" => "mex" [ok]
Stripping archive and none attached "mex"
Building from directory "d:\ME\metree"
Archive commencing from byte offset 574976
Archive constructed 5369629 bytes
Completed archive build from "d:\ME\metree" [ok]

Regards,
Pedro

-----Original Message-----
From: ext Jon Green [mailto:jon@...]
Sent: Monday, November 09, 2009 12:24 PM
To: jasspa@yahoogroups.com; Gomes, Pedro (NSN - PT/Amadora)
Subject: Re: [jasspa] Re: New version of me-standalone


  On Mon 09/11/09 12:15 PM , "azynheira" pedro.gomes@... sent:
> Hi All,
> Steve, you were right, some replacing of "r" => "rb"
> and it seems to be working as if should. The archive is correctly
> generated now ...
> Regards,
> Pedro

Hi Pedro,

You are the first on Windows.
Is it working now? Can you build an archive, add it and it runs file in
windows?

Jon

> --- In jasspa
> @yahoogroups.com, Steven Phillips <bill@...> wrote:>
> > Initial thought is that the bfs program is not
> opening the files binary > (i.e. "r" instead of "rb"
> and "w" instead of "wb") - doesn't make a lot
> > of difference on unix but does on
> windows.>
> > Steve
> >
> > azynheira wrote:
> > >
> > >
> > > Hi Jon,
> > > I patched the makefile and some of the
> files and was able to produce a > > bfs.exe and mew32.exe files to try

> it out in Win32. The results are > > the following:
> > >
> > > 1) No crashes as you predirected!
> :P> >
> > > 2) I have some problems creating archives
> (outut below). May be it as > > to be do with the endeanness of the
> thing ....> >
> > > I'll look into it...
> > >
> > > Regards,
> > > Pedro
> > > --- cut here ---
> > > D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a
> d:\me\pedro.bfs d:\me\pt101224> > Stripping archive and none attached
> "d:\me\pedro.bfs"> > Building from directory "d:\me\pt101224"> >
> Archive commencing from byte offset
> 787040> > ERROR:
> "d:\me\pt101224/attic/Siemens.emf" size mismatch 98!=104> > ERROR:
> "d:\me\pt101224/lsdmengb.edf" size mismatch 342!=470142> > ERROR:
> "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950> > ERROR:
> "d:\me\pt101224/lsdxengb.edf" size mismatch 751!=508084> > ERROR:
> "d:\me\pt101224/old/default.emf" size mismatch 29!=30> > ERROR:
> "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86> > ERROR:
> "d:\me\pt101224/old/pedro.zip" size mismatch 742!=223701> > Archive
> constructed 393520 bytes
> > > Completed archive build from
> "d:\me\pt101224" [ok]> > ---cut here --
> > >
> > > --- In jasspa
> @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, Jon
> > > Green <jon@> wrote:
> > > >
> > > > azynheira wrote:
> > > > > Hi Jon,
> > > > > Looks nice, I'm giving it a try
> the next few days ... :P> > > >
> > > > > Do you mind if I do the Win32
> port of the stuff ?> > > >
> > > > > Regards,
> > > > > Pedro
> > > > >
> > > >
> > > > I think it all just about builds on
> Windows.> > >
> > > > I got a bfs.exe building under minGW
> with virtually no changes to > > the code last
> > > > night. I've not compiled a me32.exe
> yet but I think this should be > > fine,
> > > > possibly need to define
> fseeko=>fseek ad ftello=>ftell.> > >
> > > > Jon
> > > >
> > > >
> > > >
> > > >
> > > > > --- In jasspa
> @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, > > Jon Green
<jon@> wrote:
> > > > >> Jon Green wrote:
> > > > >>> I have just posted a new
> version of me-standalone for some more > > alpha testing.
> > > > >>>
> > > > >>> This version is
> concatenated on the bottom of the executable > > using a command
> > > > >>> line utility called
> "bfs" as follows:> > > >>>
> > > > >>> To build a bfs archive
> then simply unpack the "metree" and > > remove things
> > > > >>> that you do not want in
> the archive:> > > >>>
> > > > >>> % tar zxvf
> jasspa-metree-20091017.tar.gz> > > >>> % rm -rf ./jasspa/pixmaps> > >
> >>>
> > > > >>> Build the archive and add
> to the executable from a directory:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me ./jasspa> > > >>>
> > > > >>> Append an already
> existing archive to the executable:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me jasspa-metree-20091117.bfs> > > >>>
> > > > >>> This should now be a
> stand alone executable. If you append again > > it will
> > > > >>> remove the old archive
> and add a new one. You can list the > > archive attached
> > > > >>> to the
> executable:> > > >>>
> > > > >>> % bfs -l me
> > > > >>>
> > > > >>> You can remove the
> archive attached to the executable:> > > >>>
> > > > >>> % bfs -s me
> > > > >>>
> > > > >>> You can extract the
> archive attached to the executable which > > will extract
> > > > >>> the directory tree in the
> archive to a new directory called > > "oldarch".
> > > > >>>
> > > > >>> % bfs -x oldarch
> me> > > >>>
> > > > >>> So you can now build your
> own attachable and then add to the > > bottom. If you do
> > > > >>> not attach then
> "me" runs as normal.> > > >>>
> > > > >>> The code is NOT ported to
> windows yet but should work for most > > versions of
> > > > >>> *NIX. I have only tested
> this on Linux and Solaris so far.> > > >>>
> > > > >>> The bfs on a 64-bit build
> is a bit funny, it allows:> > > >>>
> > > > >>> % bfs -a mypath/mecw -o
> me jasspa-metree-20091117.bfs> > > >>>
> > > > >>> but does not
> allow> > > >>>
> > > > >>> % bfs -a me
> jasspa-metree-20091117.bfs> > > >>>
> > > > >>> which it should do. That
> is the only issue I have found so far.> > > >>>
> > > > >>> Have fun!
> > > > >>>
> > > > >> Here is a fix for the amd64
> issue I highlighted above.> > > >>
> > > > >>
> > > > >> cd
> /home/jon/medev/bfs-v0.1.2/> > > >> gdiff --context --minimal
> --ignore-space-change --recursive> > > >>
> "/home/jon/medev/bfs-v0.1.2/ucopy.c~" > >
> "/home/jon/medev/bfs-v0.1.2/ucopy.c"> > > >>
> > > > >> ***
> /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 > > 22:18:07.714444000
> +0000
> > > > >> ---
> /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 > > 22:19:37.927169000
> +0000
> > > > >> ***************
> > > > >> *** 145,151 ****
> > > > >> int
> > > > >> bfs_fileappend (int options,
> char *srcfile, char *destfile)> > > >> {
> > > > >> ! int status;
> > > > >> FILE *rfp;
> > > > >> FILE *wfp;
> > > > >>
> > > > >> --- 145,151 ----
> > > > >> int
> > > > >> bfs_fileappend (int options,
> char *srcfile, char *destfile)> > > >> {
> > > > >> ! int status = 0;
> > > > >> FILE *rfp;
> > > > >> FILE *wfp;
> > > > >>
> > > > >> [EXIT 1]
> > > > >>
> > > > >> Jon.
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ------------------------------------> > > >
> > > > >
> __________________________________________________________> > > >
> > > > > This is an unmoderated list, but
> new members are moderated to > > ensure that there are no spam users.
> JASSPA is not responsible for the > > content of
> > > > > any material posted to this
> list.> > > >
> > > > > To un-subscribe, send a mail
> message to> > > >
> > > > > jasspa-unsubscribe@yahoogroups.com > >
> <mailto:jasspa-unsubscribe%40yahoogroups.com>> > > >
> > > > > or visit http://groups.yahoo.com/group/jasspa > >
> > > > > <http://groups.yahoo.com/group/jasspa>
> and> > > > modify your account settings
> manually.> > > >
> > > > >
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> ______________________________________________________________________
> ____ This is an unmoderated list, but new members are moderated to
> ensure that there are no spam users. JASSPA is not responsible for the

> content of any material posted to this list.
>
> To un-subscribe, send a mail message to
>
> jasspa-unsubscribe@yahoogroups.com
> or visit http://groups.yahoo.com/group/jasspa andmodify your account
settings manually.
>
>
> Yahoo! Groups Links
>
> Individual Email | Traditional
>
> jasspa-unsubscribe@yahoogroups.com
>
>
---- Message sent via KC WebMail - http://webmail.mistral.net/

Just some additional observerations:

I can only make it work if I execute the binary (on Windows, please note) by
using .exe postfix - This means that if I have a bundled ME called emacs.exe:
1) Running emacs - DOES NOT WORK....
2) Running emacs.exe - WORKS!!

Just more 50 wierd cents!

Pedro

--- In jasspa@yahoogroups.com, "Gomes, Pedro (NSN - PT/Amadora)"
<pedro.gomes@...> wrote:
>
> Hi,
> Yes, after Steve's suggestion ITS ALIVE :-) ... (add mad laughter at
> will :-))
>
> The archive is built correctly and the integrity is correct (by using
> -t), and the .exe file produced does recognize the internal fs if I use
> bfs://foobar ... It works correctly!
>
> Production log:
> D:\ME\src\std2\bfs-v0.1.1>bfs -a mypath/mecw -o me ./jasspa
> Copying "mypath/mecw" => "me"
> Error: Cannot access file "mypath/mecw"
> Copied "mypath/mecw" => "me" [fail]
>
> D:\ME\src\std2\bfs-v0.1.1>bfs -a ..\src\mew32.exe -o mex d:\ME\metree
> Copying "..\src\mew32.exe" => "mex"
> Copied "..\src\mew32.exe" => "mex" [ok]
> Stripping archive and none attached "mex"
> Building from directory "d:\ME\metree"
> Archive commencing from byte offset 574976
> Archive constructed 5369629 bytes
> Completed archive build from "d:\ME\metree" [ok]
>
> Regards,
> Pedro
>
> -----Original Message-----
> From: ext Jon Green [mailto:jon@...]
> Sent: Monday, November 09, 2009 12:24 PM
> To: jasspa@yahoogroups.com; Gomes, Pedro (NSN - PT/Amadora)
> Subject: Re: [jasspa] Re: New version of me-standalone
>
>
>  On Mon 09/11/09 12:15 PM , "azynheira" pedro.gomes@... sent:
> > Hi All,
> > Steve, you were right, some replacing of "r" => "rb"
> > and it seems to be working as if should. The archive is correctly
> > generated now ...
> > Regards,
> > Pedro
>
> Hi Pedro,
>
> You are the first on Windows.
> Is it working now? Can you build an archive, add it and it runs file in
> windows?
>
> Jon
>
> > --- In jasspa
> > @yahoogroups.com, Steven Phillips <bill@> wrote:>
> > > Initial thought is that the bfs program is not
> > opening the files binary > (i.e. "r" instead of "rb"
> > and "w" instead of "wb") - doesn't make a lot
> > > of difference on unix but does on
> > windows.>
> > > Steve
> > >
> > > azynheira wrote:
> > > >
> > > >
> > > > Hi Jon,
> > > > I patched the makefile and some of the
> > files and was able to produce a > > bfs.exe and mew32.exe files to try
>
> > it out in Win32. The results are > > the following:
> > > >
> > > > 1) No crashes as you predirected!
> > :P> >
> > > > 2) I have some problems creating archives
> > (outut below). May be it as > > to be do with the endeanness of the
> > thing ....> >
> > > > I'll look into it...
> > > >
> > > > Regards,
> > > > Pedro
> > > > --- cut here ---
> > > > D:\ME\src\std2\bfs-v0.1.1>bfs.exe -a
> > d:\me\pedro.bfs d:\me\pt101224> > Stripping archive and none attached
> > "d:\me\pedro.bfs"> > Building from directory "d:\me\pt101224"> >
> > Archive commencing from byte offset
> > 787040> > ERROR:
> > "d:\me\pt101224/attic/Siemens.emf" size mismatch 98!=104> > ERROR:
> > "d:\me\pt101224/lsdmengb.edf" size mismatch 342!=470142> > ERROR:
> > "d:\me\pt101224/lsdmptpt.edf" size mismatch 16!=509950> > ERROR:
> > "d:\me\pt101224/lsdxengb.edf" size mismatch 751!=508084> > ERROR:
> > "d:\me\pt101224/old/default.emf" size mismatch 29!=30> > ERROR:
> > "d:\me\pt101224/old/meemf.emf" size mismatch 83!=86> > ERROR:
> > "d:\me\pt101224/old/pedro.zip" size mismatch 742!=223701> > Archive
> > constructed 393520 bytes
> > > > Completed archive build from
> > "d:\me\pt101224" [ok]> > ---cut here --
> > > >
> > > > --- In jasspa
> > @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, Jon
> > > > Green <jon@> wrote:
> > > > >
> > > > > azynheira wrote:
> > > > > > Hi Jon,
> > > > > > Looks nice, I'm giving it a try
> > the next few days ... :P> > > >
> > > > > > Do you mind if I do the Win32
> > port of the stuff ?> > > >
> > > > > > Regards,
> > > > > > Pedro
> > > > > >
> > > > >
> > > > > I think it all just about builds on
> > Windows.> > >
> > > > > I got a bfs.exe building under minGW
> > with virtually no changes to > > the code last
> > > > > night. I've not compiled a me32.exe
> > yet but I think this should be > > fine,
> > > > > possibly need to define
> > fseeko=>fseek ad ftello=>ftell.> > >
> > > > > Jon
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > --- In jasspa
> > @yahoogroups.com <mailto:jasspa%40yahoogroups.com>, > > Jon Green
> <jon@> wrote:
> > > > > >> Jon Green wrote:
> > > > > >>> I have just posted a new
> > version of me-standalone for some more > > alpha testing.
> > > > > >>>
> > > > > >>> This version is
> > concatenated on the bottom of the executable > > using a command
> > > > > >>> line utility called
> > "bfs" as follows:> > > >>>
> > > > > >>> To build a bfs archive
> > then simply unpack the "metree" and > > remove things
> > > > > >>> that you do not want in
> > the archive:> > > >>>
> > > > > >>> % tar zxvf
> > jasspa-metree-20091017.tar.gz> > > >>> % rm -rf ./jasspa/pixmaps> > >
> > >>>
> > > > > >>> Build the archive and add
> > to the executable from a directory:> > > >>>
> > > > > >>> % bfs -a mypath/mecw -o
> > me ./jasspa> > > >>>
> > > > > >>> Append an already
> > existing archive to the executable:> > > >>>
> > > > > >>> % bfs -a mypath/mecw -o
> > me jasspa-metree-20091117.bfs> > > >>>
> > > > > >>> This should now be a
> > stand alone executable. If you append again > > it will
> > > > > >>> remove the old archive
> > and add a new one. You can list the > > archive attached
> > > > > >>> to the
> > executable:> > > >>>
> > > > > >>> % bfs -l me
> > > > > >>>
> > > > > >>> You can remove the
> > archive attached to the executable:> > > >>>
> > > > > >>> % bfs -s me
> > > > > >>>
> > > > > >>> You can extract the
> > archive attached to the executable which > > will extract
> > > > > >>> the directory tree in the
> > archive to a new directory called > > "oldarch".
> > > > > >>>
> > > > > >>> % bfs -x oldarch
> > me> > > >>>
> > > > > >>> So you can now build your
> > own attachable and then add to the > > bottom. If you do
> > > > > >>> not attach then
> > "me" runs as normal.> > > >>>
> > > > > >>> The code is NOT ported to
> > windows yet but should work for most > > versions of
> > > > > >>> *NIX. I have only tested
> > this on Linux and Solaris so far.> > > >>>
> > > > > >>> The bfs on a 64-bit build
> > is a bit funny, it allows:> > > >>>
> > > > > >>> % bfs -a mypath/mecw -o
> > me jasspa-metree-20091117.bfs> > > >>>
> > > > > >>> but does not
> > allow> > > >>>
> > > > > >>> % bfs -a me
> > jasspa-metree-20091117.bfs> > > >>>
> > > > > >>> which it should do. That
> > is the only issue I have found so far.> > > >>>
> > > > > >>> Have fun!
> > > > > >>>
> > > > > >> Here is a fix for the amd64
> > issue I highlighted above.> > > >>
> > > > > >>
> > > > > >> cd
> > /home/jon/medev/bfs-v0.1.2/> > > >> gdiff --context --minimal
> > --ignore-space-change --recursive> > > >>
> > "/home/jon/medev/bfs-v0.1.2/ucopy.c~" > >
> > "/home/jon/medev/bfs-v0.1.2/ucopy.c"> > > >>
> > > > > >> ***
> > /home/jon/medev/bfs-v0.1.2/ucopy.c~ 2009-11-08 > > 22:18:07.714444000
> > +0000
> > > > > >> ---
> > /home/jon/medev/bfs-v0.1.2/ucopy.c 2009-11-08 > > 22:19:37.927169000
> > +0000
> > > > > >> ***************
> > > > > >> *** 145,151 ****
> > > > > >> int
> > > > > >> bfs_fileappend (int options,
> > char *srcfile, char *destfile)> > > >> {
> > > > > >> ! int status;
> > > > > >> FILE *rfp;
> > > > > >> FILE *wfp;
> > > > > >>
> > > > > >> --- 145,151 ----
> > > > > >> int
> > > > > >> bfs_fileappend (int options,
> > char *srcfile, char *destfile)> > > >> {
> > > > > >> ! int status = 0;
> > > > > >> FILE *rfp;
> > > > > >> FILE *wfp;
> > > > > >>
> > > > > >> [EXIT 1]
> > > > > >>
> > > > > >> Jon.
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ------------------------------------> > > >
> > > > > >
> > __________________________________________________________> > > >
> > > > > > This is an unmoderated list, but
> > new members are moderated to > > ensure that there are no spam users.
> > JASSPA is not responsible for the > > content of
> > > > > > any material posted to this
> > list.> > > >
> > > > > > To un-subscribe, send a mail
> > message to> > > >
> > > > > > jasspa-unsubscribe@yahoogroups.com > >
> > <mailto:jasspa-unsubscribe%40yahoogroups.com>> > > >
> > > > > > or visit http://groups.yahoo.com/group/jasspa > >
> > > > > > <http://groups.yahoo.com/group/jasspa>
> > and> > > > modify your account settings
> > manually.> > > >
> > > > > >
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > ______________________________________________________________________
> > ____ This is an unmoderated list, but new members are moderated to
> > ensure that there are no spam users. JASSPA is not responsible for the
>
> > content of any material posted to this list.
> >
> > To un-subscribe, send a mail message to
> >
> > jasspa-unsubscribe@yahoogroups.com
> > or visit http://groups.yahoo.com/group/jasspa andmodify your account
> settings manually.
> >
> >
> > Yahoo! Groups Links
> >
> > Individual Email | Traditional
> >
> > jasspa-unsubscribe@yahoogroups.com
> >
> >
> ---- Message sent via KC WebMail - http://webmail.mistral.net/
>

Hello All,
Attached a fix for the reported problem…
Was just a matter of getting the executable name via the Win32 calls (GetModuleFileName). Worked fine in Un*x but not in Windows … :-))

<<main.c>>
Regards,
Pedro

Gomes, Pedro (NSN - PT/Amadora) wrote:
> [Attachment(s) <#TopText> from Gomes, Pedro (NSN - PT/Amadora) included
> below]
>
> Hello All,
> Attached a fix for the reported problem…
> Was just a matter of getting the executable name via the Win32 calls
> (GetModuleFileName). Worked fine in Un*x but not in Windows … :-))
>
> <<main.c>>
> Regards,
> Pedro
>
>
> Attachment(s) from Gomes, Pedro (NSN - PT/Amadora)
>
> 1 of 1 File(s)
>
> main.c <http://d.yimg.com/kq/groups/1188037/1405524053/name/main%2Ec>
>

Hi Pedro,

Thanks for this. I would never have found this as I always use the full name
via a short-cut.

I've run out of time but merged your changes in. I investigated BFS further on
Windows and there were a number of problems:

i) The file strip did not work - kept appending new versions.
ii) Compression was not working on Vista (tmpfp() seems to fail??)

I've also sorted out some porting issues as "me" was not building in MS-DEV.

I've fixed the archive file timestamps in Windows and UNIX.

I've built a windows "me" binary and new "bfs" utility, the source is also
posted to Jasspa site. There is no Linux today as I've run out of time and
Windows has consumed it all (grump)!

Its all a bit new still but I hope this source set is a little better than the
last.

Regards
Jon.

Jon Green wrote:
> Gomes, Pedro (NSN - PT/Amadora) wrote:
>> [Attachment(s) <#TopText> from Gomes, Pedro (NSN - PT/Amadora) included
>> below]
>>
>> Hello All,
>> Attached a fix for the reported problem…
>> Was just a matter of getting the executable name via the Win32 calls
>> (GetModuleFileName). Worked fine in Un*x but not in Windows … :-))
>>
>> <<main.c>>
>> Regards,
>> Pedro
>>
>>
>> Attachment(s) from Gomes, Pedro (NSN - PT/Amadora)
>>
>> 1 of 1 File(s)
>>
>> main.c <http://d.yimg.com/kq/groups/1188037/1405524053/name/main%2Ec>
>>
>
> Hi Pedro,
>
> Thanks for this. I would never have found this as I always use the full name
> via a short-cut.
>
> I've run out of time but merged your changes in. I investigated BFS further on
> Windows and there were a number of problems:
>
> i) The file strip did not work - kept appending new versions.
> ii) Compression was not working on Vista (tmpfp() seems to fail??)
>
> I've also sorted out some porting issues as "me" was not building in MS-DEV.
>
> I've fixed the archive file timestamps in Windows and UNIX.
>
> I've built a windows "me" binary and new "bfs" utility, the source is also
> posted to Jasspa site. There is no Linux today as I've run out of time and
> Windows has consumed it all (grump)!
>
> Its all a bit new still but I hope this source set is a little better than the
> last.
>
> Regards
> Jon.
>


I'v now posted a Linux 2.6 version.
Also an incorrect windows bfs.exe was posted - I have uploaded the correct
version.

Jon

Jon Green wrote:

> I'v now posted a Linux 2.6 version.
> Also an incorrect windows bfs.exe was posted - I have uploaded the correct
version.
>
> Jon
>

There is also an apple version as well now.

Jon.

Hi All,
One thing I noticed and would like to ask your opinion is, currently the
timestamps of the files when copied to the bfs is the creation file of bfs
itself.

In my opinion this should be changed so the original file's timestamp is copied
along when the bfs is created.

What do you think?


Regards
Pedro

On Tue 24/11/09 11:34 AM , "azynheira" pedro.gomes@... sent:
> Hi All,
> One thing I noticed and would like to ask your opinion is, currently the
> timestamps of the files when copied to the bfs is the creation file of bfs
> itself.
> In my opinion this should be changed so the original file's timestamp is
> copied along when the bfs is created.
> What do you think?
>
>
> Regards
> Pedro
>

Hi Pedro,

Yes this is the plan (see the attributes in BFS structure) in addition to the
file attributes and properties etc.
I have not done this at present because I can get away without and this first
cut is proof of concept.
So it is in the plan, the plan is not yet completely implemented.

The bfs.txt (or something like that) that roughly describes the file structure
contains some information as to where I was heading. Whilst I know it is very
rough, then if you look in that and then decide what is missing. Symbolic links
are an obvious one, this requires a different type of node data which contains a
reference to the referring file.

Thanks for the thought.

Regards
Jon



>
>
> ------------------------------------
>
> __________________________________________________________________________
> This is an unmoderated list, but new members are moderated to ensure that
> there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
>
> To un-subscribe, send a mail message to
>
> jasspa-unsubscribe@yahoogroups.com
> or visit http://groups.yahoo.com/group/jasspa andmodify your account settings
manually.
>
>
> Yahoo! Groups Links
>
> Individual Email | Traditional
>
> jasspa-unsubscribe@yahoogroups.com
>
>
---- Message sent via KC WebMail - http://webmail.mistral.net/