Author Topic: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"  (Read 15139 times)

roguebear

  • Community Member
  • Posts: 17
  • Hero Points: 0
Gary has made a good job about Convert Keil UV workspace to slickedit
http://community.slickedit.com/index.php?topic=45.0

new versions download of this macro  It can create right Project Properties and translate  a source file one time
http://community.slickedit.com/index.php?topic=2382.0


A question about slickedit display the files like keil, not solved...to be continue
http://community.slickedit.com/index.php?topic=2421.0
« Last Edit: December 12, 2007, 01:05:15 am by roguebear »

Gary

  • Community Member
  • Posts: 43
  • Hero Points: 5
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #1 on: December 05, 2007, 12:20:27 am »
Thank you for the feedback. Currently the missing project properties is a limitation - only the import of folders/files is supported. However I am thinking about remotely controlling uVision from SlickEdit to do the build instead of supporting the command line interface of Keil's build tools - this is also due to the fact that I am not 100% aware of all the options used in the .uv2 file - another reason is that there are different tools such as c51/cx51 a51/ax51 l51/lx51/lp5 which I am aware of.

May I ask if this would be an an acceptable option for you?

Cheers
Gary
« Last Edit: December 05, 2007, 12:42:55 am by Gary »

roguebear

  • Community Member
  • Posts: 17
  • Hero Points: 0
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #2 on: December 05, 2007, 05:03:40 am »
Gary:
    Thank your for your ardour.
    "I am thinking about remotely controlling uVision from SlickEdit to do the build instead of supporting the command line interface of Keil's build tools ---GRAY",  that's a excellent, perfect cool things, maybe a hard job. I am puzzle why the slickedit
don't support this tool?

    Keil is the best tool in 51 and arm.  99% engnieer in the embeded system use it.  others maybe use sdcc and so on.

    If you change the options for build or link, you will find the "control string" in the Options for target ->C51 A51 BLLocate tab . I think maybe if the extension is .c , keil use c51.exe, the externsion is .a or .a51... keil use a51.exe.
 
    with your leadership, this thread will be helpfull and significative.
    I am not familarwith slick-c program. so all the things i can do is to feedback to you what i know.
    I am here. I am waiting.......
« Last Edit: December 11, 2007, 04:53:59 am by roguebear »

roguebear

  • Community Member
  • Posts: 17
  • Hero Points: 0
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #3 on: December 07, 2007, 07:00:41 am »
when we create custom project:

I found may be the bugs in slickedit project settings,     at the properties -> tools tab.
   under "Compile".there is only one externsion ".s" supported by slickedt.
   if we want set it like this:
/************************************************/
Compile
       *.a51 *.asm *.a *.src
       *.c51 *.c
/************************************************/
     
we must open the file "usrprjtemplates.vpt" under slickedit config drectory, we will see
<Rule
    InputExts="*.s"
    OutputExts="*.o"
    LinkObject="1">
   <Exec CmdLine='as -o "%bd%n.o" "%f"'/>
</Rule>
between two sections . one is [debug] , the other is [release].

then we can modify the two sections  like this

.......................
.......................
<Rule
    InputExts="*.a51;*.a;*.src;*.asm;*.as"
    OutputExts="*.o"
    LinkObject="1">
   <Exec CmdLine='a51 debug'/>
</Rule>
<Rule
    InputExts="*.c51;*.c"
    OutputExts="*.o"
    LinkObject="1">
   <Exec CmdLine='a51 debug'/>
</Rule>


.......................
.......................

<Rule
    InputExts="*.a51;*.a;*.src;*.asm;*.as"
    OutputExts="*.o"
    LinkObject="1">
   <Exec CmdLine='a51 release'/>
</Rule>
<Rule
    InputExts="*.c51;*.c"
    OutputExts="*.o"
    LinkObject="1">
   <Exec CmdLine='a51 release'/>
</Rule>
         

 Bugs: 1: these settings only can be modified manually. Can slikcedit add settings for file externsion here?
                2: even use this way, if we change the "command line" options under [debug]compile->tools->tools name->compile, the  [release]compile->tools->tools name->compile will be affected.
« Last Edit: December 07, 2007, 07:07:58 am by roguebear »

Gary

  • Community Member
  • Posts: 43
  • Hero Points: 5
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #4 on: December 09, 2007, 08:25:33 am »
Thanks for the input - some of your suggestions are implemented in version 0.9.1 - http://community.slickedit.com/index.php?topic=2382.msg10117#msg10117


roguebear

  • Community Member
  • Posts: 17
  • Hero Points: 0
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #5 on: December 11, 2007, 05:00:27 am »
Thanks for GARY and HS2

   I will modify and focus on this post continuously.  I will try my best to coordinate all the posts about keil .


there is another bugs:
   1: when translate, the file externsion must be *.c and *.a51, not *.C and *.A51
   2: when translate *.a51,  whatever the content of file, the A51.exe can report errors.


i think the right rules translating the source file is under control of keil's setting?  should we add options tab for translate. build...
 i insert
_xmlcfg_set_attribute(seProjectHandle,nodeIndex,"Dialog","_java_options_form Compiler");
into the uvproconv.e   , use the options for java to show the example.

we must edit a new form like the project setting in keil, and program more....it's a hard work,  maybe no worth of doing this.


so i use keil to add or remove file form project, to complier and debug, to lint files use pclint. use slickedit to edit and the sample translate.
the terrible and make me crazy thing is SlickEdit  not provide  the possibility to display the dependencies for each source file in the project window like keil.
http://community.slickedit.com/index.php?topic=2421.0





« Last Edit: December 11, 2007, 07:18:40 am by roguebear »

roguebear

  • Community Member
  • Posts: 17
  • Hero Points: 0
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #6 on: January 07, 2008, 09:16:10 am »
Convert IAR workspace to slickedit....................   :o ;D :D 8) :-[

Barak

  • Community Member
  • Posts: 13
  • Hero Points: 1
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #7 on: August 12, 2009, 06:33:32 am »
Thanks heaps for this macro - it has made my life much easier.

I have made a couple of changes to the macro so that I can actually use the keil uVision2 IDE to compile the application too.
The configurations/project names were being truncated to 8 bytes long, which was preventing me from extracting the complete configuration to pass to uVision2.
I have added a KeilBuild and a KeilRebuild command that use the project names/keil configs to call uVision2 from the command line to excecute the build/rebuild and then dump the output in the build window.

Made a couple more changes that have it all working properly, with build output dumped correctly, can either use uvision3 or uvision2 depending on what it finds.
« Last Edit: August 13, 2009, 07:00:28 am by Barak »

koji

  • Community Member
  • Posts: 21
  • Hero Points: 0
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #8 on: September 22, 2009, 09:47:30 am »
Thanks heaps for this macro - it has made my life much easier.

I have made a couple of changes to the macro so that I can actually use the keil uVision2 IDE to compile the application too.
The configurations/project names were being truncated to 8 bytes long, which was preventing me from extracting the complete configuration to pass to uVision2.
I have added a KeilBuild and a KeilRebuild command that use the project names/keil configs to call uVision2 from the command line to excecute the build/rebuild and then dump the output in the build window.

Made a couple more changes that have it all working properly, with build output dumped correctly, can either use uvision3 or uvision2 depending on what it finds.
the accessories can't be downloaded.

Barak

  • Community Member
  • Posts: 13
  • Hero Points: 1
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #9 on: September 24, 2009, 01:41:00 am »
Let see if this works...

Robert Hall

  • Community Member
  • Posts: 30
  • Hero Points: 2
Re: about the bug of Gary's macro "Convert Keil UV workspace to slickedit"
« Reply #10 on: October 29, 2015, 09:20:38 pm »
I thought I would give this macro a try in 19.0.2.5 64-bit and at line 971 I'm getting an error:

def_vsbuild_signal_port not declared.

Any help or suggestions?

Maybe  I missed something.

(Keil version 4, btw)