Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Command line compiler
Sun, Jan 19 2014 11:01 AMPermanent Link

Leslie

Hi,

I do not seem to be able to provide the proper params to the commad line compiler. EWB framework is installed in a none default location, which is set with -fp, yet I recieve this error: "Cannot find unit file WebForms.wbs in the current project directory or in the compiler search paths". Even if the framework path is added to the system PATH the error is the same.

Cheers,
Leslie
Sun, Jan 19 2014 3:16 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

Leslie,

I gave it a quick try and i can't make it work either. Looks like a bug
so i created an incident report to have Tim see it first thing next week.


In my case the framework is in the default location but specifying

-fp"C:\Program Files (x86)\Elevate Web Builder\framework" and/or
-fs"C:\Program Files (x86)\Elevate Web Builder\framework" results in the
same error as you. Also tried adding \ to end of path and putting space
in between -fp or -fs and path but still same error.


Raul

On 1/19/2014 11:01 AM, Leslie wrote:
> I do not seem to be able to provide the proper params to the commad line compiler. EWB framework is installed in a none default location, which is set with -fp, yet I recieve this error: "Cannot find unit file WebForms.wbs in the current project directory or in the compiler search paths". Even if the framework path is added to the system PATH the error is the same.
Sun, Jan 19 2014 5:35 PMPermanent Link

Leslie

Raul,

thanks for the confirmation.

Cheers,
Leslie
Tue, Jan 21 2014 2:41 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< I do not seem to be able to provide the proper params to the commad line
compiler. EWB framework is installed in a none default location, which is
set with -fp, yet I recieve this error: "Cannot find unit file WebForms.wbs
in the current project directory or in the compiler search paths". Even if
the framework path is added to the system PATH the error is the same. >>

Yep, this is a bug - the paths were being parsed incorrectly because they
weren't being wrapped with double-quotes after being read from the
command-line.  This didn't show up in testing because I was passing a
command-line parameter for the framework path(s) that didn't include spaces.

A fix will be in build 2.

Tim Young
Elevate Software
www.elevatesoft.com


Fri, Feb 14 2014 10:52 AMPermanent Link

Matthew Jones

Could this bug exist for the -SP option too? I can't get it to work, but the -fp
worked;

/Matthew Jones/
Fri, Feb 14 2014 11:00 AMPermanent Link

Matthew Jones

Scratch that! I was just copying to FinalBuilder and realised I didn't have the
..wbp extension on the file name, and added that and it worked...

/Matthew Jones/
Image