Author Topic: New Build Tool Is Disabled  (Read 4202 times)

spowers

  • Community Member
  • Posts: 46
  • Hero Points: 0
New Build Tool Is Disabled
« on: June 11, 2008, 08:19:37 pm »
I added a new tool and it shows up in the tool list but its grayed out and disabled.


It runs a script with the command: %wp/buildmeister/cxxtest/RunUnitTests.sh -%rp

Anyone have a clue what is going on here?

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3396
  • Hero Points: 465
Re: New Build Tool Is Disabled
« Reply #1 on: June 12, 2008, 01:32:47 pm »
Does the tool have "Command is a Slick-C(R) macro" checked?  If so, and the start of the command coincides with a Slick-C command that is currently disabled, then there you go.

spowers

  • Community Member
  • Posts: 46
  • Hero Points: 0
Re: New Build Tool Is Disabled
« Reply #2 on: June 12, 2008, 06:15:12 pm »
No it doesnt... when I remade the tool it seemed to work ok....


I do have a follow up question however... Is it possible to have a new tool call its dependencies tool... similar to how Build does it?

aka if I have a tool called "Test" on one project it should call "Test" on its dependencies.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3396
  • Hero Points: 465
Re: New Build Tool Is Disabled
« Reply #3 on: June 12, 2008, 06:42:05 pm »
Well, yes and no.

No, it's not a published feature, and no, not through the GUI.

However, if you are willing to editor your project file, you can add
a project spec to the "CallTarget" tag.  For example:

Code: [Select]
<CallTarget
Project="test13.vpj"
Config="Debug"
Target="doSomething"/>
<Exec CmdLine="dir"/>

This isn't exactly a simple solution, because it won't use the project dependencies you set up.  I will file a feature request to provide and option to make custom build rules call like-named targets in dependent projects.

spowers

  • Community Member
  • Posts: 46
  • Hero Points: 0
Re: New Build Tool Is Disabled
« Reply #4 on: June 13, 2008, 01:53:02 pm »
Well, yes and no.

No, it's not a published feature, and no, not through the GUI.

However, if you are willing to editor your project file, you can add
a project spec to the "CallTarget" tag.  For example:

Code: [Select]
<CallTarget
Project="test13.vpj"
Config="Debug"
Target="doSomething"/>
<Exec CmdLine="dir"/>

This isn't exactly a simple solution, because it won't use the project dependencies you set up.  I will file a feature request to provide and option to make custom build rules call like-named targets in dependent projects.



That would be a great addition!