Anyone used the command line compiler successfully yet? I'm trying to
convert my EWB1 command lines, and getting a missing WebCore error, but
the -sp path is set to include the library. I'm wondering if the
library is supposed to have the main source...

--

Matthew Jones

Matthew Jones wrote:

>  command line compiler ... I'm trying to

Okay, this is the current batch file I'm testing with:

"C:\Program Files (x86)\Elevate Web Builder
2\bin\ewbcc\win32\ewbcc.exe"
D:\Src\MyProject\WebBuilder2\AdminBnx2.wbp -lp"C:\Program Files
(x86)\Elevate Web Builder 2\library"

This gets me an error:
Compiling project AdminBnx2..
[Error] WebCore.wbs (17,6): Cannot find unit file WebDOM.wbs in the
current project directory or in the compiler search paths
[Error] uServerInterfaces.wbs (5,6): Referenced unit compilation
failed, compilation aborted


If I add the library with -sp as well, I get:
Compiling project AdminBnx2..
[Error] uServerInterfaces.wbs (5,6): Cannot find unit file WebCore.wbs
in the current project directory or in the compiler search paths
[Error] fAdminWelcome.wbs (6,5): Referenced unit compilation failed,
compilation aborted

This is being executed in the project directory. It compiles fine in
the IDE.

Hmm, I see by looking in the project config file that I have a search
path set which contains a customised webcore.wbs. If I change it from
"uses WebDOM" to "uses webdom" the case of the error message changes. I
therefore wonder if the problem is that the search path is not working
somehow - but surely if it finds webcore.wbs it shouldn't assume all
the files are in that location?

I've experimented more, but can't push it to work. Clues welcome, as
would a "Make me a command line for this project" option in the IDE. 8-)


--

Matthew Jones


(MyProject changed to protect the innocent, I never name projects like
that!)

Matthew,

<< Okay, this is the current batch file I'm testing with: >>

What happens if you tell it to ignore the project configuration (-ic) ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> What happens if you tell it to ignore the project configuration (-ic)
> ?

Nothing substantially different - I did try that. It can't find any
units then.

--

Matthew Jones

Matthew,

I can't reproduce what you're seeing here.  I've tried two projects, and they both compile fine.  This is the last one that I tried (ignore the directory differences, of course, I'm using the development directories):

M:\products\source\ewb2\ewbcc>ewbcc "c:\ewbtest\menutest\menutest.wbp" -lp"m:\products\source\ewb2\library";"m:\products\source\ewb2\interfaces" -co
Using project configuration file c:\ewbtest\menutest\menutest.wbc
Compiling project menutest..
Success (0 hints, 0 warnings, 0 errors)
Emitted c:\ewbtest\menutest\output\menutest.js (total size is 498677 bytes - compressed)
Emitted c:\ewbtest\menutest\output\menutest.html (total size is 216532 bytes - compressed)
Copied c:\ewbtest\menutest\adug_ide.png to c:\ewbtest\menutest\output (total size is 142409 bytes)
Project menutest - compiled successfully

Can you email me your project ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> -lp"m:\products\source\ewb2\library";"m:\products\source\ewb2\interfac
> es"

Hmm, you have double quotes around your semi-colon. My semi-colon is
within the quotes. (How unusual!) I'll try that soon.

--

Matthew Jones

Okay, I've emailed, and then discovered with another test that the
problem is that the command line compiler is not liking the spaces in
the paths. It was the only difference between Tim's and mine, and I
took a copy of the files and put them somewhere with no spaces and it
works for me too. Tim has email on this too.

Sorry for adding another delay to the next update, but this will be
worth it. 8-)

--

Matthew Jones

Yes - all paths with space must be in double quotes.  That is standard in Windows.

Walter

On 9/22/2015 4:19 AM, Matthew Jones wrote:
> Hmm, you have double quotes around your semi-colon. My semi-colon is
> within the quotes. (How unusual!) I'll try that soon.

There are no quotes around the semicolon - quotes are around file
systems paths and semicolon is simply a separator.

Raul

Walter Matte wrote:

> Yes - all paths with space must be in double quotes.  That is
> standard in Windows.

But that's what it not working. The quotes are around the path, but it
is not working to make it work properly.

--

Matthew Jones