> 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!
>

... 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

Message 3 of 10
, Nov 9, 2009

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
>
>
>
>

azynheira

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

Message 4 of 10
, Nov 9, 2009

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 ....

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

Message 9 of 10
, Nov 9, 2009

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!!