Alaska Software Inc. - Re: Compiling problems

	Author	Topic: Re: Compiling problems
	Andreas Herdt	Re: Compiling problems on Wed, 08 Oct 2014 13:17:15 +0200 This was fetched from the newsgroup preview.xbase++.20 Hi Jan, When debugging a target (F9) the project builder (pbuild.exe) is started for building the currently selected target which is marked bold in the project manager. In this area the workbench has changed behaviour contrary to earlier versions of the IDE where the entire project was build. If an exe is marked as active target pbuild /t:<name>.exe will not consider any other target such as dlls in the project. Only the executable is updated. If you have changes in source files that belong to more then one target or if you have changes in a source that belongs to a target different from the currently selected active one, then first build the project (Alt+F9) before running the debugger (F9). If you observe something different then please post to this newsgroup, or alternatively to the german speaking counterpart, more detailed information. What is the name of the target and dll in your project. What is the name of the modified prg. To what target does the prg belong to? Does it belong to more then one target? What is the exact output in the message window. Performing the build manually from the command shell - does the behaviour differ? (You need to execute pbuild in the same way as shown in the message window). Additionally: There is no need to manually delete the intermediates and targets manually. Just klick on "Clean Project". With my best regards, Andreas Herdt Alaska Software -------------------------------------------------------------------- Technical Support: support@alaska-software.com News Server: news.alaska-software.com Homepage: http://www.alaska-software.com WebKnowledgeBase: http://www.alaska-software.com/kbase.shtm Fax European Office: +49 (0) 61 96 - 77 99 99 23 Fax US Office: +1 (646) 218 1281 -------------------------------------------------------------------- "Jan Escholt" wrote in message news:50f1f17$4ef794f0$485e@news.alaska-software.com... > Hi Andreas, > > I had some more tests. But the behavor is the same - changing some code > and hitting F9 tells my that the code has been compiled in the message > window. But the starting app hasn't been changed. I deleted all obj, lib, > res, def, exp files. Made a Clean Project, a Rebuild Dependencies, changed > the project directoy to the standard - nothing changes. Only after a > Rebuild Project the code changes are accepted. > > Hitting F9 gives me allways the message that the exe has been compiled. > Only the exe is mentioned. Even if I only changed code in a dll. Looks > like the dll is never compiled just by hitting F9! > > And yes, I have one exe and 12 dll in the project with my own code. > > Jan > > Am 30.09.2014 um 10:33 schrieb "Andreas Herdt": >> Hi Jan, >> >> Some things seem to be clear to me. Your project consists of more then >> one target. I assume that one target is an executable, at least one >> target >> is a dll target. >> >>> I deleted all this files once more, additional all lib, def, res, exp. >>> Hit F9 again, only the same three prg are compiled, now the Message >>> is: "[Fatal Error]: ALK 4001: cannot open file ".\drucken.lib"". First >>> of all: Shurely this file cannot be opened because it hasen't been >>> created >> >> In the case F9 is pressed then the current target is build and the >> debugger >> is started. The workbench prints this build step to the message window: >> >> Pbuild.exe project.xpj "/t:test.exe" >> >> In exactly this case where all intermediates are deleted by you, what >> happens >> if you execute Alt+F9 (Build project)? This should rebuild all targets >> now >> including "drucken.dll" where "drucken.lib" is created as intermediate. >> >>> I deleted all obj, exe, dll and made a F9 after changing one line of >>> code. Only three of more than 50 prg in this project have been >>> compiled! But the workbench tells me "[Hint]: DONE [HINT]: DBG: Client >>> has exited (Code -1073741515, Possible DLL version conflict)". Oh no! >>> Not again this "Possible DLL conflict"! This one drove me crazy with >>> VX, and >> >> This one goes into the same direction. The intermediates are deleted then >> only one target is implicitly created before the debugger is started. >> What >> I do not understand is that there seem to be outdated libraries in the >> PATH. I assume that one or more of your own dlls are loaded that have >> been created with Xbase++ version 1.9. >> >>> If I recompile everything the exe or dll has been changed. >> >> I assume that you mean the option "Rebuild project" from the workbench's >> Build menu. If this is done, does your application startup with F9? >> >>> If I change some code in one prg and hit F9, something is compiled but >>> the exe or dll has not been changed. >> >> I can not believe this one. If prg is compiled then because of the >> requirement >> of the current target is to be linked. Are you able to specify this case >> in a more detailed mannor? >> >> With my best regards, >>
	Jan Escholt	Re: Compiling problems on Thu, 09 Oct 2014 07:24:44 +0200 Hi Andreas, hmmm. No good change. Why did you do this? I allways did F9 after a code change. The advantage was - I change some code, hit F9, eveyrything that has ben changed is compiled, and the appstarts in debug mode. With just one keystroke. Now I have to do one keystroke, wait for finishing, and hit another one. I would appreciate if you would change it back to the old behaviour. And I deleted everything manually just in despair because everythong else didn't work. That this didn't work because "this is not a bug, it's a feature" wasn't clear to my mind. Jan Am 08.10.2014 um 13:17 schrieb "Andreas Herdt": > This was fetched from the newsgroup preview.xbase++.20 > > Hi Jan, > > When debugging a target (F9) the project builder (pbuild.exe) is started > for building the currently selected target which is marked bold in the > project manager. > > In this area the workbench has changed behaviour contrary to earlier > versions of the IDE where the entire project was build. > > If an exe is marked as active target pbuild /t:<name>.exe will not consider > any other target such as dlls in the project. Only the executable is > updated. > > If you have changes in source files that belong to more then one target or > if you have changes in a source that belongs to a target different from the > currently selected active one, then first build the project (Alt+F9) before > running the debugger (F9). > > If you observe something different then please post to this newsgroup, or > alternatively to the german speaking counterpart, more detailed > information. > > What is the name of the target and dll in your project. > > What is the name of the modified prg. > > To what target does the prg belong to? Does it belong to more then one > target? > > What is the exact output in the message window. > > Performing the build manually from the command shell - does the behaviour > differ? (You need to execute pbuild in the same way as shown in the > message window). > > Additionally: There is no need to manually delete the intermediates and > targets > manually. Just klick on "Clean Project". > > With my best regards, >
	Andreas Herdt	Re: Compiling problems on Thu, 09 Oct 2014 10:25:01 +0200 Hi Jan, When the entire project is implicitly build then it is not possible to run one target of the project and modify another one at the same point of time. Think about working on a client and a server - you like to modify the client and need to stop the server for recreating the client. What we like to have is a configuration at this place - you can choose what behaviour you want to have. In the meantime - press Alt+F9 then F9 and enjoy debuggung Andreas Herdt Alaska Software -------------------------------------------------------------------- Technical Support: support@alaska-software.com News Server: news.alaska-software.com Homepage: http://www.alaska-software.com WebKnowledgeBase: http://www.alaska-software.com/kbase.shtm Fax European Office: +49 (0) 61 96 - 77 99 99 23 Fax US Office: +1 (646) 218 1281 -------------------------------------------------------------------- "Jan Escholt" wrote in message news:8201410$e0cd5b4$122f2@news.alaska-software.com... > Hi Andreas, > > hmmm. No good change. Why did you do this? I allways did F9 after a code > change. The advantage was - I change some code, hit F9, eveyrything that > has ben changed is compiled, and the appstarts in debug mode. With just > one keystroke. Now I have to do one keystroke, wait for finishing, and hit > another one. I would appreciate if you would change it back to the old > behaviour. > > And I deleted everything manually just in despair because everythong else > didn't work. That this didn't work because "this is not a bug, it's a > feature" wasn't clear to my mind. > > Jan > > Am 08.10.2014 um 13:17 schrieb "Andreas Herdt": >> This was fetched from the newsgroup preview.xbase++.20 >> >> Hi Jan, >> >> When debugging a target (F9) the project builder (pbuild.exe) is started >> for building the currently selected target which is marked bold in the >> project manager. >> >> In this area the workbench has changed behaviour contrary to earlier >> versions of the IDE where the entire project was build. >> >> If an exe is marked as active target pbuild /t:<name>.exe will not >> consider >> any other target such as dlls in the project. Only the executable is >> updated. >> >> If you have changes in source files that belong to more then one target >> or >> if you have changes in a source that belongs to a target different from >> the >> currently selected active one, then first build the project (Alt+F9) >> before >> running the debugger (F9). >> >> If you observe something different then please post to this newsgroup, or >> alternatively to the german speaking counterpart, more detailed >> information. >> >> What is the name of the target and dll in your project. >> >> What is the name of the modified prg. >> >> To what target does the prg belong to? Does it belong to more then one >> target? >> >> What is the exact output in the message window. >> >> Performing the build manually from the command shell - does the behaviour >> differ? (You need to execute pbuild in the same way as shown in the >> message window). >> >> Additionally: There is no need to manually delete the intermediates and >> targets >> manually. Just klick on "Clean Project". >> >> With my best regards, >>

Author

Topic: Re: Compiling problems

Re: Compiling problems
on Wed, 08 Oct 2014 13:17:15 +0200

This was fetched from the newsgroup preview.xbase++.20

Hi Jan,

When debugging a target (F9) the project builder (pbuild.exe) is started
for building the currently selected target which is marked bold in the
project manager.

In this area the workbench has changed behaviour contrary to earlier
versions of the IDE where the entire project was build.

If an exe is marked as active target pbuild /t:<name>.exe will not consider
any other target such as dlls in the project. Only the executable is 
updated.

If you have changes in source files that belong to more then one target or
if you have changes in a source that belongs to a target different from the
currently selected active one, then first build the project (Alt+F9) before
running the debugger (F9).

If you observe something different then please post to this newsgroup, or
alternatively to the german speaking counterpart, more detailed information.

What is the name of the target and dll in your project.

What is the name of the modified prg.

To what target does the prg belong to? Does it belong to more then one 
target?

What is the exact output in the message window.

Performing the build manually from the command shell - does the behaviour
differ? (You need to execute pbuild in the same way as shown in the
message window).

Additionally: There is no need to manually delete the intermediates and 
targets
manually. Just klick on "Clean Project".

With my best regards,

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Jan Escholt" wrote in message 
news:50f1f17$4ef794f0$485e@news.alaska-software.com...
> Hi Andreas,
>
> I had some more tests. But the behavor is the same - changing some code 
> and hitting F9 tells my that the code has been compiled in the message 
> window. But the starting app hasn't been changed. I deleted all obj, lib, 
> res, def, exp files. Made a Clean Project, a Rebuild Dependencies, changed 
> the project directoy to the standard - nothing changes. Only after a 
> Rebuild Project the code changes are accepted.
>
> Hitting F9 gives me allways the message that the exe has been compiled. 
> Only the exe is mentioned. Even if I only changed code in a dll. Looks 
> like the dll is never compiled just by hitting F9!
>
> And yes, I have one exe and 12 dll in the project with my own code.
>
> Jan
>
> Am 30.09.2014 um 10:33 schrieb "Andreas Herdt":
>> Hi Jan,
>>
>> Some things seem to be clear to me. Your project consists of more then
>> one target. I assume that one target is an executable, at least one 
>> target
>> is a dll target.
>>
>>> I deleted all this files once more, additional all lib, def, res, exp.
>>> Hit F9 again, only the same three prg are compiled, now the Message
>>> is: "[Fatal Error]: ALK 4001: cannot open file ".\drucken.lib"". First
>>> of all: Shurely this file cannot be opened because it hasen't been
>>> created
>>
>> In the case F9 is pressed then the current target is build and the 
>> debugger
>> is started. The workbench prints this build step to the message window:
>>
>>     Pbuild.exe project.xpj "/t:test.exe"
>>
>> In exactly this case where all intermediates are deleted by you, what
>> happens
>> if you execute Alt+F9 (Build project)? This should rebuild all targets 
>> now
>> including "drucken.dll" where "drucken.lib" is created as intermediate.
>>
>>> I deleted all obj, exe, dll and made a F9 after changing one line of
>>> code. Only three of more than 50 prg in this project have been
>>> compiled! But the workbench tells me "[Hint]: DONE [HINT]: DBG: Client
>>> has exited (Code -1073741515, Possible DLL version conflict)". Oh no!
>>> Not again this "Possible DLL conflict"! This one drove me crazy with
>>> VX, and
>>
>> This one goes into the same direction. The intermediates are deleted then
>> only one target is implicitly created before the debugger is started. 
>> What
>> I do not understand is that there seem to be outdated libraries in the
>> PATH. I assume that one or more of your own dlls are loaded that have
>> been created with Xbase++ version 1.9.
>>
>>> If I recompile everything the exe or dll has been changed.
>>
>> I assume that you mean the option "Rebuild project" from the workbench's
>> Build menu. If this is done, does your application startup with F9?
>>
>>> If I change some code in one prg and hit F9, something is compiled but
>>> the exe or dll has not been changed.
>>
>> I can not believe this one. If prg is compiled then because of the
>> requirement
>> of the current target is to be linked. Are you able to specify this case
>> in a more detailed mannor?
>>
>> With my best regards,
>>

Jan Escholt

Re: Compiling problems
on Thu, 09 Oct 2014 07:24:44 +0200

Hi Andreas,

hmmm. No good change. Why did you do this? I allways did F9 after a code 
change. The advantage was - I change some code, hit F9, eveyrything that 
has ben changed is compiled, and the appstarts in debug mode. With just 
one keystroke. Now I have to do one keystroke, wait for finishing, and 
hit another one. I would appreciate if you would change it back to the 
old behaviour.

And I deleted everything manually just in despair because everythong 
else didn't work. That this didn't work because "this is not a bug, it's 
a feature" wasn't clear to my mind.

Jan

Am 08.10.2014 um 13:17 schrieb "Andreas Herdt":
> This was fetched from the newsgroup preview.xbase++.20
>
> Hi Jan,
>
> When debugging a target (F9) the project builder (pbuild.exe) is started
> for building the currently selected target which is marked bold in the
> project manager.
>
> In this area the workbench has changed behaviour contrary to earlier
> versions of the IDE where the entire project was build.
>
> If an exe is marked as active target pbuild /t:<name>.exe will not consider
> any other target such as dlls in the project. Only the executable is
> updated.
>
> If you have changes in source files that belong to more then one target or
> if you have changes in a source that belongs to a target different from the
> currently selected active one, then first build the project (Alt+F9) before
> running the debugger (F9).
>
> If you observe something different then please post to this newsgroup, or
> alternatively to the german speaking counterpart, more detailed
> information.
>
> What is the name of the target and dll in your project.
>
> What is the name of the modified prg.
>
> To what target does the prg belong to? Does it belong to more then one
> target?
>
> What is the exact output in the message window.
>
> Performing the build manually from the command shell - does the behaviour
> differ? (You need to execute pbuild in the same way as shown in the
> message window).
>
> Additionally: There is no need to manually delete the intermediates and
> targets
> manually. Just klick on "Clean Project".
>
> With my best regards,
>

Andreas Herdt

Re: Compiling problems
on Thu, 09 Oct 2014 10:25:01 +0200

Hi Jan,

When the entire project is implicitly build then it is not possible to run
one target of the project and modify another one at the same point of
time. Think about working on a client and a server - you like to modify
the client and need to stop the server for recreating the client.

What we like to have is a configuration at this place - you can choose
what behaviour you want to have.

In the meantime - press Alt+F9 then F9 and enjoy debuggung

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Jan Escholt" wrote in message 
news:8201410$e0cd5b4$122f2@news.alaska-software.com...
> Hi Andreas,
>
> hmmm. No good change. Why did you do this? I allways did F9 after a code 
> change. The advantage was - I change some code, hit F9, eveyrything that 
> has ben changed is compiled, and the appstarts in debug mode. With just 
> one keystroke. Now I have to do one keystroke, wait for finishing, and hit 
> another one. I would appreciate if you would change it back to the old 
> behaviour.
>
> And I deleted everything manually just in despair because everythong else 
> didn't work. That this didn't work because "this is not a bug, it's a 
> feature" wasn't clear to my mind.
>
> Jan
>
> Am 08.10.2014 um 13:17 schrieb "Andreas Herdt":
>> This was fetched from the newsgroup preview.xbase++.20
>>
>> Hi Jan,
>>
>> When debugging a target (F9) the project builder (pbuild.exe) is started
>> for building the currently selected target which is marked bold in the
>> project manager.
>>
>> In this area the workbench has changed behaviour contrary to earlier
>> versions of the IDE where the entire project was build.
>>
>> If an exe is marked as active target pbuild /t:<name>.exe will not 
>> consider
>> any other target such as dlls in the project. Only the executable is
>> updated.
>>
>> If you have changes in source files that belong to more then one target 
>> or
>> if you have changes in a source that belongs to a target different from 
>> the
>> currently selected active one, then first build the project (Alt+F9) 
>> before
>> running the debugger (F9).
>>
>> If you observe something different then please post to this newsgroup, or
>> alternatively to the german speaking counterpart, more detailed
>> information.
>>
>> What is the name of the target and dll in your project.
>>
>> What is the name of the modified prg.
>>
>> To what target does the prg belong to? Does it belong to more then one
>> target?
>>
>> What is the exact output in the message window.
>>
>> Performing the build manually from the command shell - does the behaviour
>> differ? (You need to execute pbuild in the same way as shown in the
>> message window).
>>
>> Additionally: There is no need to manually delete the intermediates and
>> targets
>> manually. Just klick on "Clean Project".
>>
>> With my best regards,
>>