Problem with v18

[DanW]

Notice the path in the command below.  It has a %rp.   v17 didnt do this.

CallTarget -t "vsbuild"
---------- 'vsbuild' Project: 'images\vxworks\ic_vxworks.vpj' - 'Release' ---------- VSLICKERRORPATH="F:\workspace\sw\product\SF260-HLD\develop\app\ic\images\vxworks\%rp"
vsbuild command can't change workspace, project, config, or target. Use CallTarget


and here the section in the project file:
         <Target
            Name="vsbuild"
            MenuCaption="&amp;vsbuild"
            RunFromDir="%rp"
            ShowOnMenu="Never"
            CaptureOutputWith="ProcessBuffer">
            <Exec CmdLine='"%(VSLICKBIN1)vsbuild" make "%w" "%r" -cppmake'/>
         </Target>
         <Target
            Name="vsrebuild"
            MenuCaption="&amp;vsrebuild"
            ShowOnMenu="Never"
            CaptureOutputWith="ProcessBuffer"
            RunFromDir="%rp">
            <Exec CmdLine='"%(VSLICKBIN1)vsbuild" rebuild "%w" "%r" -cpprebuild'/>
         </Target>

whereas, v17 did this when compiling the vsbuild and rebuild commands: (note it did not add %rp to the end of the path)
VSLICKERRORPATH="f:\workspace\sw\product\SF260-HLD\develop\app\ic\images\vxworks"
cd ..\..\..\..
cd app\common\messaging
make -f Makefile all

[Clark]

So far no luck reproducing any problem here but it's probably because I can't figure out what CallTarget -t "vsbuild" means exactly. I need some exact XML syntax if that's what it refers to. Thanks

[DanW]

Notice the %rp in the VSLICKERRORPATH= line
my guess is, it didn't expand the %rp variable which caused it to fail running vsbuild.

[DanW]

seems similar to this issue.  Can someone check...
http://community.slickedit.com/index.php/topic,9379.msg39922.html#msg39922

[Clark]

seems similar to this issue.  Can someone check...
http://community.slickedit.com/index.php/topic,9379.msg39922.html#msg39922

I don't think it's related. It only fixes a %oe problem.

If you post a small workspace and project that illustrates this problem, I'll be able to reproduce what you're seeing.

[DanW]

The command that it is failing has
Command line:    "%(VSLICKBIN1)vsbuild rebuild %w %r -cpprebuild"
Run from dir: %rp

and it returns this when run:
vsbuild command can't change workspace, project, config, or target. Use CallTarget

[Lee]

Can you post your .vpj file so we can see all the targets?

[DanW]

here it is

[Lee]

So much for a simple test case.

Try changing vsrebuild target to:
        <Exec CmdLine='"%(VSLICKBIN1)vsbuild" rebuild %w %r -cpprebuild'/>
instead of:
        <Exec CmdLine='"%(VSLICKBIN1)vsbuild rebuild %w %r -cpprebuild"'/>

I think the wrong thing is quoted there, I am not sure it ever worked to be honest.

[DanW]

Now I get error "File not found"
--------- 'vsbuild' Project: 'images\vxworks\ic_vxworks.vpj' - 'Release' ---------- VSLICKERRORPATH="F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks"
"C:\PROGRA~1\SLICKE~4.0X6\win\vsbuild build F:\workspace\sw\product\SF280\develop\app\ic\ic_vxworks.vpw F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks\ic_vxworks.vpj -cpprebuild"
vsbuild: File not found (C:\PROGRA~1\SLICKE~4.0X6\win\vsbuild build F:\workspace\sw\product\SF280\develop\app\ic\ic_vxworks.vpw F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks\ic_vxworks.vpj -cpprebuild)

maybe I should try installing v18 in a c:\slick18 dir

[Clark]

Post the new vpj file. Thanks

[DanW]

tried moving slickedit to c:\SE18 (thinking that the space was causing it)
didn't work.

---------- 'vsbuild' Project: 'images\vxworks\ic_vxworks.vpj' - 'Release' ---------- VSLICKERRORPATH="F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks"
"C:\SE18\win\vsbuild build F:\workspace\sw\product\SF280\develop\app\ic\ic_vxworks.vpw F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks\ic_vxworks.vpj -cpprebuild"
vsbuild: File not found (C:\SE18\win\vsbuild build F:\workspace\sw\product\SF280\develop\app\ic\ic_vxworks.vpw F:\workspace\sw\product\SF280\develop\app\ic\images\vxworks\ic_vxworks.vpj -cpprebuild)

[DanW]

and the workspace & project are where the error shows.

[Clark]

Looks like you did the change backwards and made more incorrect double quoted stuff.

The double quotes need to be around the program name which is "<path>vsbuild".

[Clark]

You need to adjust your .vpj file to make this work. First, fix the double quoting like we noted.

The limitation is that you can't change the target for vsbuild any more. We can't support your exact .vpj file any more. Sounds bad right...not really. Previous to v18 there were A LOT of screwy problems with vsbuild. Most notable commands inside the target were not executed in order. Now they are!!! You are using a workaround for this which is no longer needed.

Here's what you have:

      <Target
        Name="Build"
        MenuCaption="&amp;Build"
        CaptureOutputWith="ProcessBuffer"
        Deletable="0"
        SaveOption="SaveWorkspaceFiles"
        RunFromDir="%rp"
        DependsRef="Release"
        ClearProcessBuffer="1">
        <CallTarget Target="CompileSysAUtils"/>
        <CallTarget Target="CompileSysALib"/>
        <CallTarget Target="vsbuild"/>
        <CallTarget Target="Munch"/>
        <CallTarget Target="CompileMunch"/>
        <CallTarget Target="GenSymbols"/>
        <CallTarget Target="CompileSymTbl"/>
        <CallTarget Target="FinalLink"/>
        <Exec CmdLine="echo"/>
      </Target>


Here's what you will need now:


      <Target
        Name="Build"
        MenuCaption="&amp;Build"
        CaptureOutputWith="ProcessBuffer"
        Deletable="0"
        SaveOption="SaveWorkspaceFiles"
        RunFromDir="%rp"
        DependsRef="Release"
        ClearProcessBuffer="1">
        <CallTarget Target="CompileSysAUtils"/>
        <CallTarget Target="CompileSysALib"/>
        <Exec CmdLine='"%(VSLICKBIN1)vsbuild" build %w %r -cpprebuild'/>
        <CallTarget Target="Munch"/>
        <CallTarget Target="CompileMunch"/>
        <CallTarget Target="GenSymbols"/>
        <CallTarget Target="CompileSymTbl"/>
        <CallTarget Target="FinalLink"/>
      </Target>

Let me know if you have any trouble.

FYI: The v18 vsbuild supports executing multiple Exec lines now but the GUI doesn't support it yet.