D.gnu - Work on D front end compilation
- Jonathan Andrew (13/13) Jul 29 2002 OK, I'm starting this thread mostly so people can post their progress
- Jan Knepper (4/17) Jul 29 2002 STOP STOP STOP!!!
- Jan Knepper (4/17) Jul 29 2002 If you want to help, request CVS access so you can access the latest
- Jan Knepper (10/23) Jul 29 2002 OK, I just updated the .tar.gz. at http://www.opend.org/
- Jonathan Andrew (5/16) Jul 29 2002 Hmm, could you put me on the CVS? I was a little wary before because I
- Jan Knepper (2/18) Jul 29 2002
- Jonathan Andrew (2/5) Jul 29 2002 Frankly, no. :\
- andy (4/13) Jul 29 2002 start here www.cvshome.org
- Jonathan Andrew (3/8) Jul 29 2002 Thanks, I'll have to read through this tonight.
- Juan Carlos Arevalo Baeza (6/12) Jul 30 2002 For Windows, I'd recommend TortoiseCVS over WinCVS. They use the same
- Jonathan Andrew (5/5) Jul 30 2002 I'll be doing all my work in Linux, so as for right now, its going to
- V. Krishnakumar (6/10) Jul 31 2002 Actually, using cvs from the commandline is much more comfortable than f...
- Juan Carlos Arevalo Baeza (12/15) Jul 31 2002 from
OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux. On that note, I've started writing a billion little functions that to get rid of all the undefined references to backend methods that pop up when you build. i.e. // JON: stub function struct elem * MulExp::toElem(IRState *irs) { printf("MulExp::toElem() in expression.c\n"); } Is this worthwhile do you think? -Jon
Jul 29 2002
STOP STOP STOP!!! THIS IS ALL ALREADY DONE!!! Jan Jonathan Andrew wrote:OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux. On that note, I've started writing a billion little functions that to get rid of all the undefined references to backend methods that pop up when you build. i.e. // JON: stub function struct elem * MulExp::toElem(IRState *irs) { printf("MulExp::toElem() in expression.c\n"); } Is this worthwhile do you think? -Jon
Jul 29 2002
If you want to help, request CVS access so you can access the latest sources! Jan Jonathan Andrew wrote:OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux. On that note, I've started writing a billion little functions that to get rid of all the undefined references to backend methods that pop up when you build. i.e. // JON: stub function struct elem * MulExp::toElem(IRState *irs) { printf("MulExp::toElem() in expression.c\n"); } Is this worthwhile do you think? -Jon
Jul 29 2002
OK, I just updated the .tar.gz. at http://www.opend.org/ Download it and you probably will find all these things already done. I have tried to do it in such a way that I could leave the original code as untouched as possible so that upgrading to a newer front-end would be as easy as possible. Please READ the messages in this newsgroup as I do update it frequently. The last thing we want is double work as there is going to be enough work to do. Jan Jonathan Andrew wrote:OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux. On that note, I've started writing a billion little functions that to get rid of all the undefined references to backend methods that pop up when you build. i.e. // JON: stub function struct elem * MulExp::toElem(IRState *irs) { printf("MulExp::toElem() in expression.c\n"); } Is this worthwhile do you think? -Jon
Jul 29 2002
Jan Knepper wrote:OK, I just updated the .tar.gz. at http://www.opend.org/ Download it and you probably will find all these things already done. I have tried to do it in such a way that I could leave the original code as untouched as possible so that upgrading to a newer front-end would be as easy as possible. Please READ the messages in this newsgroup as I do update it frequently. The last thing we want is double work as there is going to be enough work to do. JanHmm, could you put me on the CVS? I was a little wary before because I felt I might break something, but now it seems like it will keep me from duplicating anybody's work. -Jon
Jul 29 2002
You know how to use CVS? Jonathan Andrew wrote:Jan Knepper wrote:OK, I just updated the .tar.gz. at http://www.opend.org/ Download it and you probably will find all these things already done. I have tried to do it in such a way that I could leave the original code as untouched as possible so that upgrading to a newer front-end would be as easy as possible. Please READ the messages in this newsgroup as I do update it frequently. The last thing we want is double work as there is going to be enough work to do. JanHmm, could you put me on the CVS? I was a little wary before because I felt I might break something, but now it seems like it will keep me from duplicating anybody's work. -Jon
Jul 29 2002
Jan Knepper wrote:You know how to use CVS?Frankly, no. :\
Jul 29 2002
start here www.cvshome.org If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge) Jonathan Andrew wrote:Jan Knepper wrote:You know how to use CVS?Frankly, no. :\
Jul 29 2002
andy wrote:start here www.cvshome.org If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge)Thanks, I'll have to read through this tonight. -Jon
Jul 29 2002
"andy" <acoliver apache.org> wrote in message news:3D45F2BC.8070903 apache.org...For Windows, I'd recommend TortoiseCVS over WinCVS. They use the same core, IIRC, but Tortoise's interface is... awesome. Salutaciones, JCABstart here www.cvshome.org If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge)You know how to use CVS?Frankly, no. :\
Jul 30 2002
I'll be doing all my work in Linux, so as for right now, its going to be command line all the way. If I find a nice graphical CVS proggy for linux I will be sure to let the group know. Thanks for letting me know about these other programs though. -Jon
Jul 30 2002
"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3D46EC31.CAE65C6E ece.arizona.edu...I'll be doing all my work in Linux, so as for right now, its going to be command line all the way. If I find a nice graphical CVS proggy for linux I will be sure to let the group know. Thanks for letting me know about these other programs though.Actually, using cvs from the commandline is much more comfortable than from a GUI. Even newbies (including me) use the GUI only to learn the actual underlying CVS commands and then manually run it on the commandline. -Krish
Jul 31 2002
"V. Krishnakumar" <lvimala eth.net> wrote in message news:ai8if7$nor$1 digitaldaemon.com...Actually, using cvs from the commandline is much more comfortable thanfroma GUI. Even newbies (including me) use the GUI only to learn the actual underlying CVS commands and then manually run it on the commandline.Ahem... <OT:rant> For more complex stuff like branching, you'd use command line, yes. But for your standard checkouts, diffs, updates, adds and commits, I'd seriously beg to differ. I'd never, ever use command line unless there was no other option. </OT:rant> Salutaciones, JCAB
Jul 31 2002