Logfile

[NewsArchive]

Hi Friedrich,

Would it be possible to have the logfile that is only created when
there is an error also created, perhaps in a different location, if
the command line compiling succeeds? Now the log is ONLY created if
there was an error, which is great as I use it to detect if there was
an error<g> but it would be nice to be able to show the log after a
compile even if everything went ok.

Currently it is in the sb folder for SB5 or in
CSIDL_APPDATA\LinderSoft\SetupBuilder 6\compiler.txt but perhaps you
could create a compilerok.txt in the same place as it is in C6, that
way it could easily be picked up if the compiling was good:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Would it be possible to have the logfile that is only created when
> there is an error also created, perhaps in a different location, if
> the command line compiling succeeds? Now the log is ONLY created if
> there was an error, which is great as I use it to detect if there was
> an error<g> but it would be nice to be able to show the log after a
> compile even if everything went ok.
>
> Currently it is in the sb folder for SB5 or in
> CSIDL_APPDATA\LinderSoft\SetupBuilder 6\compiler.txt but perhaps you
> could create a compilerok.txt in the same place as it is in C6, that
> way it could easily be picked up if the compiling was good:)

Yes, I think this should not be a problem.

There is already a new switch in the latest internal new SB6 build. The
command line compiler supports /L pathname now to override the folder
location of compiler.txt. Perhaps an additional command line switch /LX to
always create the compiler.txt in a selected folder.

It's on the wishlist now.

Friedrich

[NewsArchive]

Hi Friedrich,

>There is already a new switch in the latest internal new SB6 build. The
>command line compiler supports /L pathname now to override the folder
>location of compiler.txt. Perhaps an additional command line switch /LX to
>always create the compiler.txt in a selected folder.

Cool. One thing: If you make the log always available, would it be
possible to somehow easily identify if there was an error? As it is
right now I just check for the existence of the compiler.txt to check
if there was an error. Also with what I'm doing the command line is
already breaking down due to OS limits<g>

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>There is already a new switch in the latest internal new SB6 build. The
>>command line compiler supports /L pathname now to override the folder
>>location of compiler.txt. Perhaps an additional command line switch /LX
>>to
>>always create the compiler.txt in a selected folder.
>
> Cool. One thing: If you make the log always available, would it be
> possible to somehow easily identify if there was an error? As it is
> right now I just check for the existence of the compiler.txt to check
> if there was an error. Also with what I'm doing the command line is
> already breaking down due to OS limits<g>

There was already an impovement in Build 2153 (February 26, 2008)

IDE: If a command line compile fails, the error code level is set to the
number of errors. If the command line compile cannot be started (e.g.
project file not found), the return value is 1.

Can you use this to identify if there was an error?

Friedrich

[NewsArchive]

Hi Friedrich,

>There was already an impovement in Build 2153 (February 26, 2008)
>
>IDE: If a command line compile fails, the error code level is set to the
>number of errors. If the command line compile cannot be started (e.g.
>project file not found), the return value is 1.
>
>Can you use this to identify if there was an error?

So I can just pick it up with RunCode() in Clarion:) Cool, I was just
about to suggest that<vbg> So, do I understand this correctly:

Code 0 - compile succeeded
Code 1 - compile could not start
Code n - number of errors encountered

I already have build dependent stuff in my SB class so I'll add this
as an option for 2153 and higher and stuff this into class properties
for later inspection:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Arnór,

> So I can just pick it up with RunCode() in Clarion:) Cool, I was just
> about to suggest that<vbg> So, do I understand this correctly:
>
> Code 0 - compile succeeded
> Code 1 - compile could not start
> Code n - number of errors encountered
>
> I already have build dependent stuff in my SB class so I'll add this
> as an option for 2153 and higher and stuff this into class properties
> for later inspection:)

:) Yes, the above should work fine :)

Friedrich

[NewsArchive]

Hi Friedrich,

>:) Yes, the above should work fine :)

Cool:) So what point is there for me to make suggestions since you
have _already done everything???<g>

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>:) Yes, the above should work fine :)
>
> Cool:) So what point is there for me to make suggestions since you
> have _already done everything???<g>

<G> There are still quite a few things to do and there is lots of room for
improvements and additions ;-) All your suggestions will be heard and taken
into consideration!!!

Friedrich

[NewsArchive]

Hi Arnór,

New /LX command line compiler switch added to SB7. This switch allows you
to override the "standard" folder location of compiler.txt and the file is
always created (even if the command line compiling succeeds)

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

>New /LX command line compiler switch added to SB7. This switch allows you
>to override the "standard" folder location of compiler.txt and the file is
>always created (even if the command line compiling succeeds)

Just one question: When calling SB is it possible to detect an error
without the log? I.e. do you return an errorlevel if it fails? I may
have asked before but can't find it and don't have the SB docs in
front of me...

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Just one question: When calling SB is it possible to detect an error
> without the log? I.e. do you return an errorlevel if it fails? I may
> have asked before but can't find it and don't have the SB docs in
> front of me...

Yes, if a command line compile fails, the error code level is set to the
number of errors.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

>Yes, if a command line compile fails, the error code level is set to the
>number of errors.

In what version/build was this implemented? I don't see it in the
docs I have but I don't have the latest (I'm downloading it right now)


Am I safe to use my check for the compile.txt as an error indicator
until SB 7?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> In what version/build was this implemented? I don't see it in the
> docs I have but I don't have the latest (I'm downloading it right now)

It was this implemented in Build 2153.

SetupBuilder 6.7 -- February 2008 Update 2 -- Build 2153 (February 26, 2008)
----------------------------------------------------------------------------

IMPROVEMENT: IDE: If a command line compile fails, the error code level is
set to the number of errors. If the command line compile
cannot be started (e.g. project file not found), the return
value is 1.

> Am I safe to use my check for the compile.txt as an error indicator
> until SB 7?

Yes. The check for the compile.txt as an error indicator works for both SB6
and SB7.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

>It was this implemented in Build 2153.

Cool. I'm sticking all return codes into variable so it's available
after the program(s) finish, so this could be used as an additional
check:)

>> Am I safe to use my check for the compile.txt as an error indicator
>> until SB 7?
>
>Yes. The check for the compile.txt as an error indicator works for both SB6
>and SB7.

But only if the /LX is not used to force writing of the log file even
if no errors, right?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>Yes. The check for the compile.txt as an error indicator works for both
>>SB6 and SB7.
>
> But only if the /LX is not used to force writing of the log file even
> if no errors, right?

Right :) In SB7, if /LX is *not* used then no compile.txt is created if the
compile completed successfully. If /LX is used then compile.txt is always
created (in a specified location).

Friedrich