Asm files in SN

Asm files in SN

[leonp]

Hello, all.
	First of all I want to thank Cygnus for the great product.
	Next, I have a small problem with my Linux installation: I created the 
project which contains files of type *.S - assembler. When I tried to add 
this files to my target, this didn't work. I was able to add type ASM to 
build rules in .cfg file, but no more than that.
	Thanks ahead.

Leon Pollak
leonp@plris.com

Re: Asm files in SN

[Ben Elliston]

Hi Leon,

   	Next, I have a small problem with my Linux installation: I
   created the project which contains files of type *.S - assembler. When
   I tried to add this files to my target, this didn't work. I was able
   to add type ASM to build rules in .cfg file, but no more than that.

Note that the assembly language parser is specifically for PowerPC assembly
language.  It may not manage to detect anything useful in assembly files for
other targets.  It's possible to generate your own, if you really want to.

What kind of asm files are you trying to parse?

Cheers, Ben

Future Development features (was: Asm files in SN)

[Gilles J. Seguin]

Ben Elliston wrote:
> 
> Note that the assembly language parser is specifically for PowerPC assembly
> language.  It may not manage to detect anything useful in assembly files for
> other targets.  It's possible to generate your own, if you really want to.
> 
> What kind of asm files are you trying to parse?

I would appreciate if we can propose a whish list and future
development features list, with desirable/important/urgent comments.

What is S-N, what features we do not want.
What we do not want Source-Navigator to become.

Gilles J. Seguin

Re: Future Development features (was: Asm files in SN)

[Syd Polk]

At 12:33 AM 7/24/00 -0400, Gilles J. Seguin wrote:
>Ben Elliston wrote:
> >
> > Note that the assembly language parser is specifically for PowerPC assembly
> > language.  It may not manage to detect anything useful in assembly 
> files for
> > other targets.  It's possible to generate your own, if you really want to.
> >
> > What kind of asm files are you trying to parse?
>
>I would appreciate if we can propose a whish list and future
>development features list, with desirable/important/urgent comments.
>
>What is S-N, what features we do not want.
>What we do not want Source-Navigator to become.
>
>Gilles J. Seguin

I would be happy to collect issues and centralize them into a web page, and 
put an ascii version of it in snavigator/TODO.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.

Re: Asm files in SN

[leonp]

At 08:57 24/07/2000 +1000, you wrote:
> >       Next, I have a small problem with my Linux installation: I
> >  created the project which contains files of type *.S - assembler. When
> >   I tried to add this files to my target, this didn't work. I was able
> >   to add type ASM to build rules in .cfg file, but no more than that.
>Note that the assembly language parser is specifically for PowerPC assembly
>language.  It may not manage to detect anything useful in assembly files for
>other targets.  It's possible to generate your own, if you really want to.
>What kind of asm files are you trying to parse?

Thank you for reply.
My case is exactly PowerPC  CPU.
But my question is not exactly about the parser (which, as I understand, 
allows me to parse source code), but about more simple thing - I want to 
build my target, which depends on several asm and C files. My attempt to 
add an asm file to the target in the Tools->Build Settings->Source 
Files->Add files does nothing, totally ignoring my asm files.
Many thanks again.



Leon Pollak
leonp@plris.com