xAce v0.5 released

18 views
Skip to first unread message

Lawrence Woodman

unread,
Dec 22, 2012, 3:14:18 AM12/22/12
to xace...@googlegroups.com
Hello all,

I have today released xAce v0.5, so a big thank you to
DuLac, Steven, Edward and especially Marcos for all your
help and advice.

https://github.com/LawrenceWoodman/xAce/archive/v0.5.zip

I have decided to release now as I have been looking at
how I can add a proper GUI to xAce and have
realised that sticking to X is a pain, so therefore have
created a fork which uses Tk. This leaves the x in xAce
out of place, so I will create a new repo and let you
know as soon as I do.

Thanks once again


Lawrence Woodman

--
vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry, CV1 2FL
Registered in England and Wales No. 06477649
http://vlifesystems.com

Marcos Cruz

unread,
Dec 24, 2012, 5:23:41 PM12/24/12
to xace...@googlegroups.com
En/Je/On 2012-12-22 08:14, Lawrence Woodman escribi� / skribis / wrote :

> I have today released xAce v0.5,

Great. Thank you for all your work, Lorry. And of course thank you to
Edward Patel too for the base work. Some time ago, when all available
was the last version by Edward Patel and your own patch, I could only
dream of an improved and updated emulator for Linux, easier to use and
more suitable for cross development, because my knowledge of C is very
limited for such a task.

> a fork which uses Tk.

I have no actual experience programming GUIs, but I can understand
things are much easier with a special library. The GUI will bring new
life to the emulator.

Do you mean the development of xAce will stop, beside fixing bugs?

> This leaves the x in xAce out of place,

Will TkAce be the name of the new program?

Marcos

--
http://programandala.net

steven

unread,
Dec 26, 2012, 8:41:09 AM12/26/12
to xace...@googlegroups.com
I have just tried to compile the new version (0.5) and failed! (with mint
14)

So I tried version .04 which compiled and runs fine.

The instructions are not very clear and easy to follow.

I did install cmake could you take another look at it please?

I do use Linux mint every day these days and found the instructions
confusing. With folks moving over from Windows 8 I think it's worth getting
the instructions perfect!


SteveSPT


-----Original Message-----
From: xace...@googlegroups.com [mailto:xace...@googlegroups.com] On Behalf
Of Marcos Cruz
Sent: 24 December 2012 22:24
To: xace...@googlegroups.com
Subject: Re: xAce v0.5 released

Marcos Cruz

unread,
Dec 26, 2012, 8:54:43 AM12/26/12
to xace...@googlegroups.com
En/Je/On 2012-12-26 13:41, steven escribi� / skribis / wrote :

> I have just tried to compile the new version (0.5) and failed! (with mint
> 14)

Which step fails and what message is shown?
>
> I did install cmake

Did you run 'cmake .' (with the dot)? I didn't the first time I used it.
Cmake needs the path to source as an argument. The dot means "the
current path". If in doubt, consult the manual with 'man cmake'.

Marcos

--
http://programandala.net

Lawrence Woodman

unread,
Dec 27, 2012, 3:04:43 AM12/27/12
to xace...@googlegroups.com
On 24/12/12 22:23, Marcos Cruz wrote:
> En/Je/On 2012-12-22 08:14, Lawrence Woodman escribi� / skribis / wrote :
>
>
> I have no actual experience programming GUIs, but I can understand
> things are much easier with a special library. The GUI will bring new
> life to the emulator.

Yes, much easier to code, more platform independent and with the
inclusion of Tcl easier to script certain parts of it.

> Do you mean the development of xAce will stop, beside fixing bugs?

Yes, pretty much, unless it's something very minor as I think it will
be better to concentrate my efforts on the new emulator, which
will have all the functionality of the old plus more.

>> This leaves the x in xAce out of place,
> Will TkAce be the name of the new program?

I wanted to get away from having a platform specific reference in the title,
so have chosen CanAce. This way if the underlying technologies changes
in the future there is no need to change the name.

I have got an early version working and will probably upload it tomorrow.


bfn


Lorry

Lawrence Woodman

unread,
Dec 27, 2012, 3:08:15 AM12/27/12
to xace...@googlegroups.com
On 26/12/12 13:41, steven wrote:
> I have just tried to compile the new version (0.5) and failed! (with mint
> 14)
>
> So I tried version .04 which compiled and runs fine.
>
> The instructions are not very clear and easy to follow.
>
> I did install cmake could you take another look at it please?
>
> I do use Linux mint every day these days and found the instructions
> confusing. With folks moving over from Windows 8 I think it's worth getting
> the instructions perfect!

I'm sorry if the instructions were confusing, however with CanAce
it should be easier to provide a single executable and the only people
needing to compile it will be those working on the code.


Lorry

Mikael O. Bonnier

unread,
Jan 1, 2013, 9:23:46 PM1/1/13
to xace...@googlegroups.com
I have today released xAce v0.5, so a big thank you to
DuLac, Steven, Edward and especially Marcos for all your
help and advice.

https://github.com/LawrenceWoodman/xAce/archive/v0.5.zip

I compiled it on Raspberry Pi with Rasbian without any warnings and now it runs fine. I haven't tested attaching tape images yet. I also compiled it on Ubuntu 10.04 on Intel PC but there I got a warning: "CMakeFiles/tape_test.dir/tape_test.c.o: In function `test_tape_attach_file_doesnt_exist':
tape_test.c:(.text+0x4ef): warning: the use of `tmpnam' is dangerous, better use `mkstemp'". I also runs well in Ubuntu.

I think the zip-file should be called xace-0.5.zip.

Lawrence Woodman

unread,
Jan 2, 2013, 8:05:37 AM1/2/13
to xace...@googlegroups.com
I'm glad that you got it running on these systems.  I am aware of the tmpnam problem but because of the nature of what I'm testing I can't think of a solution that I'm happy with.  I'm not too worried about this though as it is only in the tests not the main program.



I think the zip-file should be called xace-0.5.zip.

I agree but unfortunately the name is automatically generated by GitHub, so there is little I can do about it without fudging the tagging system.


Lorry
Reply all
Reply to author
Forward
0 new messages