I have an App that requires both an EXE and a separate DLL (used by multiple
Apps).  This is not particularly unusual, but when the project is built, I
would like both to be created (as needed based on changes) and copied to a
specific folder from which they are normally run.

Currently I have been doing this using a "make.bat" file.  Is it possible to
set up the VX Project File to do this, or should I continue to rely on my
current method?  What are the ramifications of building a VX project by use
of Pbuild from the command line or called from a batch file?

-Joe

Hi Joe,

Your are right, this is a really common issue (from my point of view).

I have played with two scenarios allready.
First trick would be to execute a makefile or bat file with help of
the Customized Tools (Menu Tools->Customize). This way I was able
to build C++ sources with vx. The bat or makefile is responsible to
to the jobs after build.

This way it not really elegant.

Another way is this:
We have an experimental Name-Value pair in pbuild.
It was designed for Alaska internal purposes. But since it is very
usefull I have scheduled this feature to be documented:


[target.exe]
  PRE_ACTION   = "Runshell line"
  POST_ACTION  = "Runshell line"
  CLEAN_ACTION = "Runshell line"

The Runshell line will be executed with RunShell() prior and after
the target is build. The Clean_Action dependency is executed when
when the project is cleaned up (pbuild -c)

Hope this helps

Joe Carrick - The Maniacc wrote:

> I have an App that requires both an EXE and a separate DLL (used by
> multiple Apps).  This is not particularly unusual, but when the project is
> built, I would like both to be created (as needed based on changes) and
> copied to a specific folder from which they are normally run.
> 
> Currently I have been doing this using a "make.bat" file.  Is it possible
> to set up the VX Project File to do this, or should I continue to rely on
> my current method?  What are the ramifications of building a VX project by
> use of Pbuild from the command line or called from a batch file?
> 
> -Joe

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

Hi Andreas,

Thanks for the reply.  The new pbuild options sound pretty nice.  Hopefully,
when it is documented there will be some examples.

-Joe

"Andreas Herdt" <andreas.herdt@alaska-research.com> wrote in message
news:VBtwNa6yDHA.2332@S15147418...
> Hi Joe,
>
> Your are right, this is a really common issue (from my point of view).
>
> I have played with two scenarios allready.
> First trick would be to execute a makefile or bat file with help of
> the Customized Tools (Menu Tools->Customize). This way I was able
> to build C++ sources with vx. The bat or makefile is responsible to
> to the jobs after build.
>
> This way it not really elegant.
>
> Another way is this:
> We have an experimental Name-Value pair in pbuild.
> It was designed for Alaska internal purposes. But since it is very
> usefull I have scheduled this feature to be documented:
>
>
> [target.exe]
>   PRE_ACTION   = "Runshell line"
>   POST_ACTION  = "Runshell line"
>   CLEAN_ACTION = "Runshell line"
>
> The Runshell line will be executed with RunShell() prior and after
> the target is build. The Clean_Action dependency is executed when
> when the project is cleaned up (pbuild -c)
>
> Hope this helps
>
> Joe Carrick - The Maniacc wrote:
>
> > I have an App that requires both an EXE and a separate DLL (used by
> > multiple Apps). This is not particularly unusual, but when the project
is
> > built, I would like both to be created (as needed based on changes) and
> > copied to a specific folder from which they are normally run.
> >
> > Currently I have been doing this using a "make.bat" file. Is it possible
> > to set up the VX Project File to do this, or should I continue to rely
on
> > my current method? What are the ramifications of building a VX project
by
> > use of Pbuild from the command line or called from a batch file?
> >
> > -Joe
>
> --
> Regards
>
>
> Andreas Herdt
>
>
> //////////////////////////////////////////////////////////////////
> 
>  Alaska Research & Development
>  Homepage: www.alaska-research.com
>  Newsgroup: nntp://news.alaska-Software.net
> 
> //////////////////////////////////////////////////////////////////

Joe,

Have you tried them? Did they solve your problem?

Joe Carrick - The Maniacc wrote:

> Thanks for the reply.  The new pbuild options sound pretty nice. 
> Hopefully, when it is documented there will be some examples.
> 
> -Joe
> 

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

I'm on holiday - I'll try them on Monday.

-Joe

"Andreas Herdt" <andreas.herdt@alaska-research.com> wrote in message
news:4Bn4Ez7yDHA.1972@S15147418...
> Joe,
>
> Have you tried them? Did they solve your problem?
>
> Joe Carrick - The Maniacc wrote:
>
> > Thanks for the reply. The new pbuild options sound pretty nice.
> > Hopefully, when it is documented there will be some examples.
> >
> > -Joe
> >
>
> --
> Regards
>
>
> Andreas Herdt
>
>
> //////////////////////////////////////////////////////////////////
> 
>  Alaska Research & Development
>  Homepage: www.alaska-research.com
>  Newsgroup: nntp://news.alaska-Software.net
> 
> //////////////////////////////////////////////////////////////////