Topic: Adding a new compiler (1 of 36), Read 140 times
Conf: Compiler support
From: Michael Baas
Date: Tuesday, August 26, 2003 11:47 AM

Hi,

I'd like to add support for a new compiler.

Here's what I've done so far:
- edit COMPILE.CNF: DEFCOMPILE=ppwz -proj.ext
- copied SAMPLE.VCS to PPWZ.VSC, edited:
if (Is_WinNT) {
Reg_Set(98," /consolefile:vcs.tmp") //Reroute stdout and stderr to
vcs.tmp
} else {
Reg_Set(98," /consolefile:vcs.tmp") //Reroute stdout to vcs.tmp
}

Shouldn't that be sufficient to compile a file?

After loading compiler-support and selecting "Compile", I get a prompt
"Project file:" and I have no idea why it get this and where to look for
the problem. Any help is much appreciated.

Tx

Michael

 

Topic: Re: Adding a new compiler (2 of 36), Read 142 times
Conf: Compiler support
From: Ted Green
Date: Tuesday, August 26, 2003 02:19 PM

At 11:48 AM 8/26/2003, you wrote:
>After loading compiler-support and selecting "Compile", I get a prompt
> "Project file:" and I have no idea why it get this and where to look for
> the problem. Any help is much appreciated.

This indicates that you don't yet have a source file open.
Therefore, first open the source file, then select {TOOLS, Compile}.

Ted.

 

Topic: Re: **SPAM** Re: Adding a new compiler (3 of 36), Read 152 times
Conf: Compiler support
From: Michael Baas
Date: Tuesday, August 26, 2003 03:54 PM



>This indicates that
you don't yet have a source file open. style="font-family:'Tahoma';">
style="font-family:'Tahoma';">>Therefore, first open the source file,
then select {TOOLS, Compile}. style="font-family:'Tahoma';">


Sorry, I had not mentioned this, but
it is open...


 


Cheers


 


Michael

 

Topic: Adding a new compiler (4 of 36), Read 142 times
Conf: Compiler support
From: Christian Ziemski
Date: Tuesday, August 26, 2003 04:44 PM

Michael, Ted:

There is a typo in C-INIT.VDM which seems to cause that problem:

Line 572 has a closing parenthesis missing:

Reg_Set(85,FILEONLY //@85 = project filename without .ext

It should be:

Reg_Set(85,FILEONLY)


Strange that no one reported problems earlier?!?!

Christian

 

Topic: Adding a new compiler (5 of 36), Read 145 times
Conf: Compiler support
From: Christian Ziemski
Date: Wednesday, August 27, 2003 02:38 AM


There are more problems...

1) If there is no file open when executing "{Tools, Compile}" the prompt "Project file:" opens as expected. Choosing a file seems to start the compiler (there is the Compiler message at the bottom of the window), but in fact there is no compiler run.
If I repeat the "{Tools, Compile}" now it looks like the same but the compiler has been really run.

2) And sometimes testing the above it happened that VEDIT switched back to the default Microsoft CL compiler (I changed COMPILE.CNF to use GCC and there is no local COMPILE.VCO).

Unfortunately I don't have much time today to look into it.
I just wanted to inform ...

Christian

 

Topic: Adding a new compiler (6 of 36), Read 147 times
Conf: Compiler support
From: Christian Ziemski
Date: Wednesday, August 27, 2003 04:49 AM

Earlier I wrote:

>There are more problems...

I found (at least one) reason for those problems:
There was an old COMPILE.CNF in C:\VEDIT\COMPILE and
that one was used while being somewhere in the compiler macros. The correct COMPILE.CNF in C:\VEDIT was ignored then.
Due to this mixture the strangest results happened.

Tip: NEVER have more than one COMPILE.CNF. And this one has to be in C:\VEDIT (Vedit's HOME)

Another one: If the file open dialog coming up after the "Project file:" prompt is canceled (without a filename) the compile macro breaks. I fixed that but will test it a bit more ...


Christian

 

Topic: Re: Adding a new compiler (12 of 36), Read 153 times
Conf: Compiler support
From: Ted Green
Date: Thursday, August 28, 2003 09:57 AM

At 04:52 AM 8/27/2003, you wrote:
>Tip: NEVER have more than one COMPILE.CNF. And this one has to be in C:\VEDIT (Vedit's HOME)

Christian:

Thank you for all your recent work on the compile macros. I will examine everything soon and update the files for the next release.

However, I would still prefer to support multiple compile.cnf files, e.g. VEDIT should first look in the current directory for a local compile.cnf file. This is better for people who use multiple compilers.

It appears that the compile macros were never updated to support long filenames with spaces. Windows requires that all pathnames with spaces be enclosed in double-quotes; this is not a VEDIT thing, but rather a Windows thing.

Ted.

 

Topic: Re: Adding a new compiler (14 of 36), Read 155 times
Conf: Compiler support
From: Christian Ziemski
Date: Thursday, August 28, 2003 02:28 PM

Ted:

you wrote:

>However, I would still prefer to support multiple compile.cnf files,
>e.g. VEDIT should first look in the current directory for a local
>compile.cnf file.

I thought COMPILE.VCO would do that.
But reading the online help again I see that local COMPILE.CNF are
allowed. O.k. I will change the macros back.

I think my problem has been that I had an old COMPILE.CNF in the
COMPILE directory which is *not* my project directory.
And that one has been loaded somewhere in the compiler macros what
gave the strange results. I'll check the Load commands for that.


>It appears that the compile macros were never updated to support
>long filenames with spaces.

Done in the macros uploaded earlier today.

>Windows requires that all pathnames with spaces be enclosed in double-quotes;
>this is not a VEDIT thing, but rather a Windows thing.

Yes. Off course! ;-)
Fortunately VEDIT's macros can work around those problems. :-)


Christian

 

Topic: Re: Adding a new compiler (16 of 36), Read 168 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Friday, September 19, 2003 02:14 PM

Yesterday I wrote:

>I think my problem has been that I had an old COMPILE.CNF in the
>COMPILE directory which is *not* my project directory.
>And that one has been loaded somewhere in the compiler macros what
>gave the strange results. I'll check the Load commands for that.

Got it!

It's the same as in SRCHFILE.VDM I sent you(Ted) last week:
Using Reg_Load() etc. without an (absolute) path is loading the file
from CUR_DIR and not from the directory the current file is in.

And CUR_DIR easily can be different. (In my case I first opened
C-INIT.VDM and then an example C-source to compile. So CUR_DIR was
C:\VEDIT\COMPILE and not C:\SRC\C-Examples.)

I fixed that by adding a Chdir(PATHONLY) just before the two relative
Reg_Load()s in C-INIT.VDM.

It's attached.


Cheers

Christian


PS: The compiler macros are able to handle pathes/filenames with
spaces in it.


(Attachment is obsolete! See newer one in this thread!)

  C-INIT(2).VDM (26KB)

 

Topic: Re: Adding a new compiler (17 of 36), Read 166 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Friday, August 29, 2003 04:13 AM


Earlier I wrote:

>I fixed that by adding a Chdir(PATHONLY) just before the two relative
>Reg_Load()s in C-INIT.VDM.

That's a bit too hard coded...
So I modified it to not changing the CUR_DIR but to load the config
files from |(PATHONLY)/compile.cnf.

C-INIT.VDM is attached again. Now it should be reasonably ready...


Christian

  C-INIT(3).VDM (26KB)

 

Topic: Re: Adding a new compiler (19 of 36), Read 159 times
Conf: Compiler support
From: Ted Green
Date: Thursday, September 04, 2003 03:10 PM

At 04:16 AM 8/29/2003, you wrote:
>C-INIT.VDM is attached again. Now it should be reasonably ready...

Thank you for the fixed c-init.vdm. I will check it soon and include it in the next release. (I am very busy this week interviewing for new employees.)

Ted.

 

Topic: Re: Adding a new compiler (20 of 36), Read 162 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Friday, September 05, 2003 05:22 PM

On 9/4/2003 3:10:31 PM, Ted Green wrote:

>Thank you for the fixed c-init.vdm. I will check it soon
>[...]

Assuming that "soon" is still in the future I decided to have another look into c-init.

Michael Baas' wish for "-name.ext" mainly let me do this.
And I didn't perfectly like the necessary modifications in the CNF files regarding double quotes.

So I modified ADD_PROJECT in C-INIT.VDM heavily.

Now it's no longer necessary to add double quotes to the -proj in the CNF files. And it should be relatively easy to add replacements like -name or -name.ext.

Since I'm enjoying some holidays with only a simple laptop and a 9600 online connection I didn't have the chance to test the new version intensively yet.
(And my girlfriend wouldn't like to see me working too much here....)
It's attached anyway.

Christian

  C-INIT(4).VDM (29KB)

 

Topic: Re: Adding a new compiler (21 of 36), Read 162 times, 2 File Attachments
Conf: Compiler support
From: Christian Ziemski
Date: Sunday, September 07, 2003 01:31 PM

On Fri, 5 Sep 2003 17:24:18 -0400, I wrote
about my modified C-INIT.VDM:

>[...] I didn't have the chance to test the new version intensively yet.
>It's attached anyway.

And everybody knows: There have been still bugs in it ;-)

Here is the new version. Better tested.

The test cases for the entries in COMPILE.CNF regarding ADD_PROJECT
were:

DEFCOMPILE=cc ... -proj.ext
DEFCOMPILE=cc ... "-proj.ext"
DEFCOMPILE=cc ... -proj.exe -proj
DEFCOMPILE=cc ... -proj.exe -proj.obj
DEFCOMPILE=cc ... "-proj.exe with space" -proj.obj
DEFCOMPILE=cc ... "-proj.exe with space"

DEFCOMPILE=cc ... -name.ext
DEFCOMPILE=cc ... "-name.ext"
DEFCOMPILE=cc ... -name.exe -name
DEFCOMPILE=cc ... -name.exe -name.obj
DEFCOMPILE=cc ... "-name.exe with space" -name.obj
DEFCOMPILE=cc ... "c:\long path\-name.exe with space"


I think I now caught all possible situations?!


While working on C-INIT.VDM I found the JAVA-implementation a bit
puzzling there. To make it working with the new easier (IMHO)
structure in ADD_PROJECT I needed to add two lines to C-JAVAVM.VDM
(only setting a flag).
So both files are attached.


Christian

PS: External testers needed!

  C-INIT(5).VDM (30KB)
  C-JAVAVM.VDM (3KB)

 

Topic: Re: Adding a new compiler (23 of 36), Read 166 times
Conf: Compiler support
From: Michael Baas
Date: Tuesday, September 09, 2003 11:42 AM



style="font-family:'Tahoma';">Hi,



> I think I now caught
all possible situations?!



Just a side-note about
"possible situations": I'm currently working with a compiler (and prepare
compiler support for it) which is implemented as a Rexx-script! So in order
to run that compiler, I need to call the Rexx-Interpreter, passing the name
of the compiler as one of the arguments. Since it seems the name of the
compiler is used to identify the required VCS, I wrote a BAT to do the call
- but I wonder if (in the long run...) it wouldn't be an idea to enable
the user to name the compiler (or directly provide the name of the
corresponding VCS in the CNF).



> PS: External testers
needed!



I will test-drive it soon.
Fortunately I don't have much time at the moment, Lydia ( href="http://lydia.mbaas.de"> href="http://lydia.mbaas.de">http://lydia.mbaas.de) is keeping me
busy ;-)



Cheers



Michael

 

Topic: Re: Adding a new compiler (24 of 36), Read 168 times
Conf: Compiler support
From: Ted Green
Date: Tuesday, September 09, 2003 03:55 PM

At 07:43 AM 9/9/2003, you wrote:
>Just a side-note about "possible situations": I'm currently working with a compiler (and prepare compiler support for it) which is implemented as a Rexx-script! So in order to run that compiler, I need to call the Rexx-Interpreter, passing the name of the compiler as one of the arguments. Since it seems the name of the compiler is used to identify the required VCS, I wrote a BAT to do the call - but I wonder if (in the long run...) it wouldn't be an idea to enable the user to name the compiler (or directly provide the name of the corresponding VCS in the CNF).

While I am very thankful for improvements such as Christian's, working on the compiler support ourselves is currently a low priority. Since the compiler support is entirely implemented in macros, we have been relying
on users to make improvements.

>I will test-drive it soon. Fortunately I don't have much time at the moment, Lydia (http://lydia.mbaas.de) is keeping me busy ;-)

Cute website. :-)) And thank you for the VEDIT link.

Ted.

 

Topic: Re: Adding a new compiler (25 of 36), Read 163 times
Conf: Compiler support
From: Christian Ziemski
Date: Tuesday, September 09, 2003 04:43 PM

Michael:

On Tue, 9 Sep 2003 11:46:03 , you wrote:

> Fortunately I don't have much time at the moment, Lydia (http://lydia.mbaas.de) is keeping me busy ;-)

Congratulations! Nice girl!


While browsing on your site a bit I found in "Surfboard von M.B.":
"Opera * die schwedische Alternative zum Internet Explorer"

Opera is from Norway, not Sweden!


And Michael, a little wish: please send your emails to Webboard in pure ASCII and not in HTML. There are mail programs and human readers who do not like HTML formated mails. Thanks.

Christian

 

Topic: AW: Adding a new compiler (34 of 36), Read 141 times
Conf: Compiler support
From: Michael Baas
Date: Tuesday, September 23, 2003 03:01 AM

Hi all,

I'm back in business again, after great vacation ;-)

> From: "Christian Ziemski"
> Congratulations! Nice girl!

Thanks ;-)

> Opera is from Norway, not Sweden!

Uups - how did that happen? Fixed - thanks.

> And Michael, a little wish: please send your emails to Webboard in
pure ASCII and not in HTML.


Actually I noticed that already. And that's very embarassing,
because I hate it myself to receive HTML-mails (as long as it isn't
really necessary). The reason why this happened was because I was trying
a new mail-software (to get rid of Outlook with all its security-flaws)
and it sended the msg in 'Styled'-format. When sending the msg I was not
aware of that, but I made sure to send mail to mailing-lists as plain
txt. So I hope this will not happen again. (Anyways - back on my office
PC now where I'm still using Outlook...)

Cheers

Michael

 

Topic: Re: Adding a new compiler (18 of 36), Read 151 times
Conf: Compiler support
From: Pauli Lindgren
Date: Tuesday, September 02, 2003 11:05 AM

On 8/28/2003 9:57:34 AM, Ted Green wrote:
>
>However, I would still prefer to support multiple
>compile.cnf files, e.g. VEDIT should first look in the
>current directory for a local compile.cnf file. This is
>better for people who use multiple compilers.

That "current directory" always causes problems, not just in compiler support but in all the places it is used. After all, Windows does not really have "current directory". So the value of CUR_DIR is is pretty much random. If it is used, it is very difficult to predict which directory Vedit uses.

I think at least the value of current directory should be saved with the project. Better still, there should be "project directory" setting for each project. Every time a project would be opened, the current directory would be set to this directory. In addition, the value could be readable from macro language the same way as CUR_DIR.

--
Pauli

 

Topic: Re: Adding a new compiler (29 of 36), Read 151 times
Conf: Compiler support
From: Ted Green
Date: Saturday, September 13, 2003 06:30 PM

At 11:05 AM 9/2/2003, you wrote:
>That "current directory" always causes problems, not just in compiler support but in all the places it is used. After all, Windows does not really have "current directory". So the value of CUR_DIR is is pretty much random. If it is used, it is very difficult to predict which directory Vedit uses.

This is why we are changing some macros to use the directory of the current file. (The file in the current buffer/window.)

The on-line help topic "Opening Files - Starting (Default) Directory for File-Open" defines exactly what CUR_DIR is. It is predictable, but not always obvious.

>I think at least the value of current directory should be saved with the project.

It is part of the project. The .PRJ files have a Chdir() command.

>Better still, there should be "project directory" setting for each project. Every time a project would be opened, the current directory would be set to this directory. In addition, the value could be readable from macro language the same way as CUR_DIR.

That is a reasonable suggestion, but I don't see how it would be used. I think it is better to simply use the directory of the current file.

Ted.


Ted.
-------------------------------------------------------------------------
Ted Green (ted@...) Greenview Data, Inc.
Web: www.... PO Box 1586, Ann Arbor, MI 48106
Tel: (734) 996-1300 Fax: (734) 996-1308 VEDIT - Text/Data/Binary Editor
-------------------------------------------------------------------------
Spam problems? www.SpamStopsHere.com blocks 99% of spam for businesses.

 

Topic: Re: Adding a new compiler (30 of 36), Read 147 times
Conf: Compiler support
From: Pauli Lindgren
Date: Monday, September 15, 2003 10:53 AM

On 9/13/2003 6:30:44 PM, Ted Green wrote:
>
>>I think at least the value of current directory should be saved with the project.
>
>It is part of the project. The .PRJ files have a Chdir()
>command.

What directory does it change to? Not to the right directory anyway. Every time I try to use CTAGS, Vedit says "TAGS file not found in this directory". Then I run my own "project" macro, which does a Chdir() to the project directory, and then CTAGS works. Next time I open the project, the directory is wrong again.

>
>>Better still, there should be "project directory" setting for each project. Every time a project would be opened, the current directory would be set to this directory. In addition, the value could be readable from macro language the same way as CUR_DIR.
>
>That is a reasonable suggestion, but I don't see
>how it would be used. I think it is better to simply
>use the directory of the current file.

That does help in some situations, but not always.

For example, the project I am currently working on consists of some 30 "modules". Each module contains one or a few .c files plus the associated .h files. The customer demands that each module must be in a separate directory.
In order to CTAGS to work, I would need to copy the TAGS file into every directory.

I have not even tried to use the compiler support in this project. It would require different compiler commands for every directory (for include path etc.). And makefile does not work if the current directory is not the directory of makefile.

In quite a many projects, at least the application files and hardware dependent files are located in different directories. In this case, I can use the compiler support if the currently open file is one of the application files (which are in the same directory as the makefile). But I can not separately compile one of the hardware dependent files from within Vedit.

Further, I am currently working on a macro that generates makefile automatically. This requires that the macro knows not just the root directory of the project but also the include path. The macro should be able to update the dependencies without re-entering the file list every time. (The same goes for Wildfile, too.) All the other project dependent settings could be stored in a datafile in the project directory, if the macro knows the project directory.

--
Pauli

 

Topic: Re: Adding a new compiler (31 of 36), Read 149 times
Conf: Compiler support
From: Lowell Dennis
Date: Monday, September 15, 2003 04:17 PM

>For example, the project I am currently
>working on consists of some 30
>"modules". Each module contains one or a
>few .c files plus the associated .h
>files. The customer demands that each
>module must be in a separate directory.
>In order to CTAGS to work, I would need
>to copy the TAGS file into every
>directory.

I had the same type of problem ... I am a BIOS developer and the BIOS source code consists of hundreds of ASM, C, and ASL files distributed across a fairly extensive directory structure. When generating the TAGS file I use the -S option to have the tag generator recurse through the directory tree. When my macro is loaded it looks in the current directory for the tagfile and if it is not found there is looks in "..\" and if it is not found there it looks in "..\..\", etc. This at least works for me. I do not know if it would work for you.

I have also totally rewritten the TAG lookup macro to support multiple instances. For example if the cursor is on "xyz" a list box with "xyz[*]" will appear allowing you to select the correct one. I wrote this some time ago and I have not kept up with some of the newer things available in later versions of Vedit. For example, I would like to make the selection box, point and click, but at this point in time I do not know if it is even possible.

I made my custom macros available to Ted some time ago, but last I spoke with him he had not had time to review them. Perhaps there are others here who would like to review them.

>Further, I am currently working on a
>macro that generates makefile
>automatically. This requires that the
>macro knows not just the root directory
>of the project but also the include
>path. The macro should be able to update
>the dependencies without re-entering the
>file list every time. (The same goes for
>Wildfile, too.) All the other project
>dependent settings could be stored in a
>datafile in the project directory, if
>the macro knows the project directory.

I would be very interested in this when you get it working.

Lowell
----------
There are 10 kinds of people.
Ones who understand binary and
Ones who don't!

 

Topic: Re: Adding a new compiler (32 of 36), Read 158 times
Conf: Compiler support
From: Ted Green
Date: Monday, September 15, 2003 04:34 PM

At 04:27 PM 9/15/2003, you wrote:
>I made my custom macros available to Ted some time ago, but last I spoke with him he had not had time to review them. Perhaps there are others here who would like to review them.

Lowell:

Please attach your macro to a message here and we can then all review your useful improvement to utags.vdm

Ted.

 

Topic: Re: Adding a new compiler (33 of 36), Read 156 times, 1 File Attachment
Conf: Compiler support
From: Lowell Dennis
Date: Monday, September 15, 2003 06:12 PM

Actually my TAG macros make use of several more general purpose macros that are divided into several files ...

ALLOC.VDM - Has macros for allocating buffers and text registers with error reporting in the status line.

STACK.VDM - has macros for implementing stacks (that allow pushing and popping of variable length data) using vedit text registers.

FILESTCK.VDM - uses STACK.VDM to implement a stack of filenames. This is used to backtrack through the tags.

PICK.VDM - uses STACK.VDM to implement a pick list. This is what is used to display the list of matching tags from with the user can choose. This is the one that I would like to improve with point and click.

TAG.VDM - is the macro that drives the whole TAG lookup process.

The following is part of my USTARTUP.VDM
Reg_Load(102,"STACK.VDM",EXTRA+NOERR)
Reg_Load(102,"ALLOC.VDM",APPEND+EXTRA+NOERR)
Reg_Load(102,"FILESTCK.VDM",APPEND+EXTRA+NOERR)
Reg_Load(102,"PICK.VDM",APPEND+EXTRA+NOERR)
Reg_Load(102,"TAG.VDM",APPEND+EXTRA+NOERR)
Key_Add("Ctrl-F",'[VISUAL EXIT] CALL(102,"TAG_LOOKUP")',OK)
Key_Add("Ctrl-B",'[VISUAL EXIT] #80=#91;CALL(102,"POP_FILE")',OK)
Key_Add("Ctrl-S",'[VISUAL EXIT] CALL(102,"GET_SYMBOL") IF (RV==0) { Search(@80,BEGIN+SET) }',OK)
Call(102,"TAG_INIT")

The code is pretty rough (this is why I wanted the review). So don't laugh or I'll take my toys and go home :-)

I hope I added enough comments for you all to follow what I am doing (sometimes I'm not even sure what I was thinking).

Lowell
----------
There are 10 kinds of people.
Ones who understand binary and
Ones who don't!

  Macros in a ZIP file

 

Topic: Re: Adding a new compiler (7 of 36), Read 148 times
Conf: Compiler support
From: Michael Baas
Date: Wednesday, August 27, 2003 05:37 AM

Thanks Christian, for pointing out the problem in C-Init. I edited this and
now I get other problems ;-/

I had a problem in my bat to launch the compiler and so the vcs.tmp was not
created. Vedit correctly reported this problem and then it went off into an
endless loop, printing "Directory not found: Einstellungen/Michael" (which
is _part_ of the path to the filename - it seems that the blanks in the
path are causing trouble, since this works fine in paths without
blanks...)

Cheers

Michael

 

Topic: Re: Adding a new compiler (8 of 36), Read 149 times
Conf: Compiler support
From: Christian Ziemski
Date: Wednesday, August 27, 2003 08:28 AM

Yes, I have problems with blanks in filenames too (of course).

But that's not sooo easy to find a fix. The compiler macros from Ted are a bit complex ...

Later.

Christian

 

Topic: Re: Adding a new compiler (9 of 36), Read 153 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Friday, August 29, 2003 04:18 AM

Michael,

you wrote:

>I had a problem in my bat to launch the compiler and so the vcs.tmp was not
> created. Vedit correctly reported this problem and then it went off into an
> endless loop, printing "Directory not found: Einstellungen/Michael" (which
> is _part_ of the path to the filename - it seems that the blanks in the
> path are causing trouble, since this works fine in paths without
> blanks...)

I fixed the "spaces in path or filename" problem:

First you have to modify COMPILE.CNF: Add surrounding double quotes to
the path/filenames, for example:

DEFCOMPILE=GCC -o "-proj.exe" "-proj.ext"


Additionally you will need a new C-INIT.VDM. It's attached.

In this new C-INIT.VDM I changed the following:

- COMPILE.CNF is *only* allowed in VEDIT's HOME now
(I hope that's ok. (Ted?)
- added double quotes in File_Open()s to allow spaces
- fixed the "Project file:" prompt code to don't
fail on canceling the Get_Filename() dialog
- fixed the already mentioned typo


For me it's working fine in some tests.
But more testers are welcome since I don't compile often.


Christian

(Attachment is obsolete! See newer one in this thread!)

  C-INIT.VDM (26KB)

 

Topic: Re: Adding a new compiler (10 of 36), Read 154 times
Conf: Compiler support
From: Michael Baas
Date: Wednesday, August 27, 2003 04:51 PM

Christian,

thanks, that was very quick!

Unfortunately it still doesn't work. It still works fine in a directory
without blanks, but in the path with blanks it does not start the
compilation. The endless loop, however, is gone :-)
Is there anything I could do to get more info which might help with the
debugging?

Cheers

Michael

P.S: I'm currently using 2 compilers. But not at the same time. So I'm
planning to have multiple compile.cnf's and extend the fileopen-macro to
copy the correct one as compile.cnf. Do you think that's safe or is there
a better way to do that?

 

Topic: Re: Adding a new compiler (11 of 36), Read 155 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Thursday, August 28, 2003 06:02 AM

Michael:

You wrote:
>Unfortunately it still doesn't work.

Blanks in path and filenames are #()/)&*§%& !!

Attached there are new compiler macros.
But please save your original ones before!

With those ones it should work.

There is one additional thing to edit in the VCS file(s):

In the :COMPILE: section the quotes must be changed to:
System('"|@(96)\vcs-tmp.bat"',DOS+NOMSG+SIMPLE)


>So I'm planning to have multiple compile.cnf's and extend >the fileopen-macro ...

I have a feeling that that's not a good idea.
But no facts for now.


Christian

  Some new compiler macros

 

Topic: Re: Adding a new compiler (13 of 36), Read 154 times
Conf: Compiler support
From: Michael Baas
Date: Thursday, August 28, 2003 12:01 PM

Hi Christian,

> With those ones it should work.

looks very good, indeed :-)
Many thanks!!!

Now I'll try and get those "find next error"-macros working...


> >So I'm planning to have multiple compile.cnf's and extend >the
fileopen-macro ...
>
> I have a feeling that that's not a good idea. But no facts for now.

:-(
Well, one step after the other, I will try i, when I'm done with all the
other stuff.
If all else fails, I can still copy these CNF's around when Vedit is closed.



Cheers

Michael

 

Topic: Re: Adding a new compiler (15 of 36), Read 160 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Friday, August 29, 2003 04:17 AM

Michael,

you wrote:

>So I'm planning to have multiple compile.cnf's

After Ted's message I modified C-INIT.VDM again (back in this regard).
It's attached.

Now you can have local COMPILE.CNF's again.


Christian

(Attachment is obsolete! See newer one in this thread!)

  C-INIT(1).VDM (26KB)

 

Topic: Re: Adding a new compiler (22 of 36), Read 144 times
Conf: Compiler support
From: Fritz Heberlein
Date: Monday, September 08, 2003 10:14 AM

> It should be:
>
> Reg_Set(85,FILEONLY)
>
>
> Strange that no one reported problems earlier?!?!
>

since it has been working for eons, at least for me, hihi ....

Fritz

 

Topic: Adding a new compiler (26 of 36), Read 142 times
Conf: Compiler support
From: Fritz Heberlein
Date: Wednesday, September 10, 2003 08:36 AM

>There is a typo in C-INIT.VDM
>which seems to cause that
>problem:
[...]

>Strange that no one reported
>problems earlier?!?!

I'm using the compiler support on a 'every day all day' basis, i.e. at least 20 times a day, and the missing bracket never has caused any problem. Interesting theoretical implication: Is "//" considered as a substitute for the closing bracket? And if so, under which circumstances is it not?

Fritz

 

Topic: Re: Adding a new compiler (27 of 36), Read 142 times
Conf: Compiler support
From: Christian Ziemski
Date: Wednesday, September 10, 2003 01:02 PM

>I'm using the compiler support on a 'every day all day' basis,
>i.e. at least 20 times a day, and the missing bracket never
>has caused any problem. Interesting theoretical implication:
>Is "//" considered as a substitute for the closing bracket?
>And if so, under which circumstances is it not?

Do you usually use it with the source file already loaded?
If yes, the macro doesn't reach the if branch with the typo.

Christian

 

Topic: Re: Adding a new compiler (28 of 36), Read 147 times
Conf: Compiler support
From: Fritz Heberlein
Date: Wednesday, September 10, 2003 02:37 PM

> Do you usually use it with the source file already loaded?

Always.

> If yes, the macro doesn't reach the if branch with the typo.

OK, got it. Thanks, Christian.

Fritz

 

Topic: Adding a new compiler (35 of 36), Read 123 times
Conf: Compiler support
From: Peter Rejto
Date: Friday, September 26, 2003 05:33 PM

On 8/26/2003 4:44:09 PM, Christian Ziemski wrote:
>Michael, Ted:
>
>There is a typo in C-INIT.VDM
>which seems to cause that
>problem:
>

Christian,

As you know I use only LATEX.VCS. Please let me know, whether it has any reference to C-INIT.VDM. In other words, should I study the present discussion.

Thanks,

-peter.

 

Topic: Re: Adding a new compiler (36 of 36), Read 120 times
Conf: Compiler support
From: Christian Ziemski
Date: Saturday, September 27, 2003 02:48 PM

Peter:

On Fri, 26 Sep 2003 17:35:34 , you wrote:

>As you know I use only LATEX.VCS. Please let me know,
>whether it has any reference to C-INIT.VDM.

The compiler support always calls C-INIT.VDM internally.
For every VCS.

But the mentioned typo only hurts when you are starting the
compile without an already loaded source file.

Christian