Author Topic: vsbuild creates a Release directory why and how to stop?  (Read 4706 times)

ehab

  • Senior Community Member
  • Posts: 285
  • Hero Points: 15
  • coding with SE is like playing music
vsbuild creates a Release directory why and how to stop?
« on: October 11, 2009, 12:01:27 am »
hi

i have configuration for build that every time i call it a [Release] directory is created?

can you please tell me how to stop this outcome.

the command line is like:

del *.cc

and invokes vsbuild.

thanks for any hints
ehab
« Last Edit: October 12, 2009, 10:42:12 am by ehab »

Graeme

  • Senior Community Member
  • Posts: 2365
  • Hero Points: 313
Re: vsbuild creates a Release directory why and how to stop?
« Reply #1 on: October 13, 2009, 08:17:08 am »
Can you describe exact steps to reproduce
e.g.
Create brand new project
Select project type of ...
On the build tab, select "all configurations"  ... or what?
On the build tab, select build system of "build without a makefile"  ... or what
On the tools tab ...  do what ...  ?

Also, what O.S. and what version of Slick?

Graeme

ehab

  • Senior Community Member
  • Posts: 285
  • Hero Points: 15
  • coding with SE is like playing music
Re: vsbuild creates a Release directory why and how to stop?
« Reply #2 on: October 13, 2009, 09:00:43 am »
hi Graeme,

thanks for the rescue : )  oky,

win 7 , SE 14.0.2.2 patched.

type of project : other ( no make file .. )
project properties ( settings for ): All Configurations
tools: pdfLatex, viewPdf, CleanAll, bitex
command line: del /F /Q  .\pdfs\*.*   ((( for the one causeing release directory creation - CleanAll ))
capture output ,to build windows, clear build : all checked

other tools don't create [Release] dir, maybe because they are calling other console apps like pdflatex... the one i have problems with is calling normal dos Del.

did any of the above help

thanks for trying Graeme.

ehab
« Last Edit: October 13, 2009, 09:03:15 am by ehab »

Graeme

  • Senior Community Member
  • Posts: 2365
  • Hero Points: 313
Re: vsbuild creates a Release directory why and how to stop?
« Reply #3 on: October 13, 2009, 09:19:48 am »
I can't reproduce the problem.  Where does your release directory get created? Maybe you could create a brand new absolute minimal project and see if you can reproduce.  Attached is the minimal project I used.  The mydel command deletes files *.xyz in the current directory so use with care.

Graeme





ehab

  • Senior Community Member
  • Posts: 285
  • Hero Points: 15
  • coding with SE is like playing music
Re: vsbuild creates a Release directory why and how to stop?
« Reply #4 on: October 13, 2009, 09:56:36 am »

i have notices with your attached blank vpj the command line in outputwindows looks like

D:\LUT\Thesis\trunk\docs>"C:\Program Files\SlickEditV14.0.2\win\vsbuild" -signal 9009 -command del /F /Q  .\pdfs\*.*

the one that causes the release directory looked like

D:\LUT\Thesis\trunk\docs>"C:\Program Files\SlickEditV14.0.2\win\vsbuild" cleanall -b D:\LUT\Thesis\trunk\docs\Chapter1_Introduction.tex -beep D:\LUT\Thesis\trunk\MainWS.vpw D:\LUT\Thesis\trunk\docs\Thesis.vpj -signal 9009
VSLICKERRORPATH="D:\LUT\Thesis\trunk\docs"
del /F /Q  .\pdfs\*.*

so what i did was i deleted my previous build command and add it again and voila [Release] dir no longer created. problem solved,

just for educational purposes what could be the reason? you don't have to waist time in investigating now since my pest has vanished : )

my thanks

Graeme

  • Senior Community Member
  • Posts: 2365
  • Hero Points: 313
Re: vsbuild creates a Release directory why and how to stop?
« Reply #5 on: October 13, 2009, 10:56:39 am »
Quote
so what i did was i deleted my previous build command and add it again and voila [Release] dir no longer created. problem solved,

just for educational purposes what could be the reason? you don't have to waist time in investigating now since my pest has vanished : )

Dunno what could be the reason.  vsbuild is a bit of a mystery to me actually.  If you type vsbuild /? on a dos cmdline you'll see what options it has.  This is how vsbuild gets invoked on my system using the mydel command in the skeleton project I posted.

vsbuild -signal 9009 -command del /f /q  *.xyz

There's no project file name in the call to vsbuild, whereas both the vpw and vpj were supplied to vsbuild in the stuff you posted.  Maybe your problem will come back and you can investigate further... !

Graeme