es40-developers

[ES40-developers] ES40 Emulator Status Update

[Camiel V. <iam...@gm...>]

Hello Everyone,

This e-mail is to inform you that I have just applied a very large
patch to CVS that affects the entire emulator. Over the past few
weeks,. we've run into the limitations of running everything in a
single clock-loop, calling devices' DoClock() functions. This leads to
wildly varying CPU speed, and does not efficiently the processing
power of modern multi-core/multi-processor CPU's.

The patch that has just been committed gets rid of the DoClock()
functions, and instead lets each device run its own threads as needed.
If you have a dual-core system, the emulated CPU could run on one
core, with the other core taking care of all other devices.

This is a patch I've been working on for a long time, and it's been a
bit of a pain keeping it in sync with all the other changes that have
happened in the past few weeks, which is why I'm committing it so soon
after the release of 0.19.

So far the good news, now the bad news:

This patch is a radical departure from the way we used to do things,
and it breaks a couple of things. The <break> menu on the Serial
console lost it's functionality. IDB doesn't work yet. And, most
importantly, this release probably introduces bugs caused by threads
accessing the same thing at the same time. These issues will all need
to be addressed in the next couple of weeks. Everyone can help out by
submitting bug reports to this list for anything that doesn't work as
expected.

You will need to install the Poco C++ libraries for the new code to compile.

The new approach also opens the door to emulating multiple CPU's,
although that is not functional yet. I'm working hard on this, but I'm
missing something in the initialization. The basic bits and pieces are
in place, but the extra cpu's never come fully online. If you think
you can help with this, please contact me.

I've created a new CVS branch ("no-threading") before this patch that
will be used for necessary bugfixes to the version 0.19 codebase.

Regards,

Camiel Vanderhoeven.

Re: [ES40-developers] ES40 Emulator Status Update

[Fausto S. <fa...@un...>]

Hello Camiel,

this is very interesting news...
Just a question about POCO libraries: which one we have to compile?  
the light version, or the enterprise?
I'm trying to compile and install the light one, but I have a problem  
because the visual studio file looks for "mc" command.

What's that command?
Do you have the same problem?

regards,
fausto

Quoting Camiel Vanderhoeven <iam...@gm...>:

> Hello Everyone,
>
> This e-mail is to inform you that I have just applied a very large
> patch to CVS that affects the entire emulator. Over the past few
> weeks,. we've run into the limitations of running everything in a
> single clock-loop, calling devices' DoClock() functions. This leads to
> wildly varying CPU speed, and does not efficiently the processing
> power of modern multi-core/multi-processor CPU's.
>
> The patch that has just been committed gets rid of the DoClock()
> functions, and instead lets each device run its own threads as needed.
> If you have a dual-core system, the emulated CPU could run on one
> core, with the other core taking care of all other devices.
>
> This is a patch I've been working on for a long time, and it's been a
> bit of a pain keeping it in sync with all the other changes that have
> happened in the past few weeks, which is why I'm committing it so soon
> after the release of 0.19.
>
> So far the good news, now the bad news:
>
> This patch is a radical departure from the way we used to do things,
> and it breaks a couple of things. The <break> menu on the Serial
> console lost it's functionality. IDB doesn't work yet. And, most
> importantly, this release probably introduces bugs caused by threads
> accessing the same thing at the same time. These issues will all need
> to be addressed in the next couple of weeks. Everyone can help out by
> submitting bug reports to this list for anything that doesn't work as
> expected.
>
> You will need to install the Poco C++ libraries for the new code to compile.
>
> The new approach also opens the door to emulating multiple CPU's,
> although that is not functional yet. I'm working hard on this, but I'm
> missing something in the initialization. The basic bits and pieces are
> in place, but the extra cpu's never come fully online. If you think
> you can help with this, please contact me.
>
> I've created a new CVS branch ("no-threading") before this patch that
> will be used for necessary bugfixes to the version 0.19 codebase.
>
> Regards,
>
> Camiel Vanderhoeven.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Camiel V. <iam...@gm...>]

Hi Fausto,

I've used the economy package, and I didn't come across that command.
I've added pre-built development (.lib) and runtime (.dll) libraries
to the download page on sourceforge.

Camiel.

On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito <fa...@un...> wrote:
> Hello Camiel,
>
>  this is very interesting news...
>  Just a question about POCO libraries: which one we have to compile?
>  the light version, or the enterprise?
>  I'm trying to compile and install the light one, but I have a problem
>  because the visual studio file looks for "mc" command.
>
>  What's that command?
>  Do you have the same problem?
>
>  regards,
>  fausto
>
>
>
>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>
>  > Hello Everyone,
>  >
>  > This e-mail is to inform you that I have just applied a very large
>  > patch to CVS that affects the entire emulator. Over the past few
>  > weeks,. we've run into the limitations of running everything in a
>  > single clock-loop, calling devices' DoClock() functions. This leads to
>  > wildly varying CPU speed, and does not efficiently the processing
>  > power of modern multi-core/multi-processor CPU's.
>  >
>  > The patch that has just been committed gets rid of the DoClock()
>  > functions, and instead lets each device run its own threads as needed.
>  > If you have a dual-core system, the emulated CPU could run on one
>  > core, with the other core taking care of all other devices.
>  >
>  > This is a patch I've been working on for a long time, and it's been a
>  > bit of a pain keeping it in sync with all the other changes that have
>  > happened in the past few weeks, which is why I'm committing it so soon
>  > after the release of 0.19.
>  >
>  > So far the good news, now the bad news:
>  >
>  > This patch is a radical departure from the way we used to do things,
>  > and it breaks a couple of things. The <break> menu on the Serial
>  > console lost it's functionality. IDB doesn't work yet. And, most
>  > importantly, this release probably introduces bugs caused by threads
>  > accessing the same thing at the same time. These issues will all need
>  > to be addressed in the next couple of weeks. Everyone can help out by
>  > submitting bug reports to this list for anything that doesn't work as
>  > expected.
>  >
>  > You will need to install the Poco C++ libraries for the new code to compile.
>  >
>  > The new approach also opens the door to emulating multiple CPU's,
>  > although that is not functional yet. I'm working hard on this, but I'm
>  > missing something in the initialization. The basic bits and pieces are
>  > in place, but the extra cpu's never come fully online. If you think
>  > you can help with this, please contact me.
>  >
>  > I've created a new CVS branch ("no-threading") before this patch that
>  > will be used for necessary bugfixes to the version 0.19 codebase.
>  >
>  > Regards,
>  >
>  > Camiel Vanderhoeven.
>  >
>  > -------------------------------------------------------------------------
>  > This SF.net email is sponsored by: Microsoft
>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  > _______________________________________________
>  > Es40-developers mailing list
>  > Es4...@li...
>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Es40-developers mailing list
>  Es4...@li...
>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Fausto S. <fa...@un...>]

Hi Camiel,

that command is related to Visual Studio (not Express version).
There're some additional file to install in order to compile with  
Visual Studio Express.

Anyway, I cannot compile it, due to some errors... some missing c  
files in the library.

Where did you find the pre-compiled windows binaries?
I searched in the sourceforge web site, but I didn't find them. Just  
the source, pre-release source and contribs packages.

regards,
fausto

Quoting Camiel Vanderhoeven <iam...@gm...>:

> Hi Fausto,
>
> I've used the economy package, and I didn't come across that command.
> I've added pre-built development (.lib) and runtime (.dll) libraries
> to the download page on sourceforge.
>
> Camiel.
>
> On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito <fa...@un...> wrote:
>> Hello Camiel,
>>
>>  this is very interesting news...
>>  Just a question about POCO libraries: which one we have to compile?
>>  the light version, or the enterprise?
>>  I'm trying to compile and install the light one, but I have a problem
>>  because the visual studio file looks for "mc" command.
>>
>>  What's that command?
>>  Do you have the same problem?
>>
>>  regards,
>>  fausto
>>
>>
>>
>>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>
>>  > Hello Everyone,
>>  >
>>  > This e-mail is to inform you that I have just applied a very large
>>  > patch to CVS that affects the entire emulator. Over the past few
>>  > weeks,. we've run into the limitations of running everything in a
>>  > single clock-loop, calling devices' DoClock() functions. This leads to
>>  > wildly varying CPU speed, and does not efficiently the processing
>>  > power of modern multi-core/multi-processor CPU's.
>>  >
>>  > The patch that has just been committed gets rid of the DoClock()
>>  > functions, and instead lets each device run its own threads as needed.
>>  > If you have a dual-core system, the emulated CPU could run on one
>>  > core, with the other core taking care of all other devices.
>>  >
>>  > This is a patch I've been working on for a long time, and it's been a
>>  > bit of a pain keeping it in sync with all the other changes that have
>>  > happened in the past few weeks, which is why I'm committing it so soon
>>  > after the release of 0.19.
>>  >
>>  > So far the good news, now the bad news:
>>  >
>>  > This patch is a radical departure from the way we used to do things,
>>  > and it breaks a couple of things. The <break> menu on the Serial
>>  > console lost it's functionality. IDB doesn't work yet. And, most
>>  > importantly, this release probably introduces bugs caused by threads
>>  > accessing the same thing at the same time. These issues will all need
>>  > to be addressed in the next couple of weeks. Everyone can help out by
>>  > submitting bug reports to this list for anything that doesn't work as
>>  > expected.
>>  >
>>  > You will need to install the Poco C++ libraries for the new code  
>>  to compile.
>>  >
>>  > The new approach also opens the door to emulating multiple CPU's,
>>  > although that is not functional yet. I'm working hard on this, but I'm
>>  > missing something in the initialization. The basic bits and pieces are
>>  > in place, but the extra cpu's never come fully online. If you think
>>  > you can help with this, please contact me.
>>  >
>>  > I've created a new CVS branch ("no-threading") before this patch that
>>  > will be used for necessary bugfixes to the version 0.19 codebase.
>>  >
>>  > Regards,
>>  >
>>  > Camiel Vanderhoeven.
>>  >
>>  > -------------------------------------------------------------------------
>>  > This SF.net email is sponsored by: Microsoft
>>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  > _______________________________________________
>>  > Es40-developers mailing list
>>  > Es4...@li...
>>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >
>>
>>
>>
>>  -------------------------------------------------------------------------
>>  This SF.net email is sponsored by: Microsoft
>>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  _______________________________________________
>>  Es40-developers mailing list
>>  Es4...@li...
>>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Camiel V. <iam...@gm...>]

Hi Fausto,

I compiled them myself. I downloaded the economy package from
http://pocoproject.org/poco/download/ and built it (both for 32-bit
windows on my laptop, and for 64-bit windows on my desktop). I have
the full Visual Studio version, apparently, mc is part of the Windows
SDK. (That question is in the POCO FAQ:
http://pocoproject.org/poco/wiki/tiki-view_faq.php?faqId=2#q10).

Camiel.

On Thu, Mar 6, 2008 at 2:05 AM, Fausto Saporito <fa...@un...> wrote:
> Hi Camiel,
>
>  that command is related to Visual Studio (not Express version).
>  There're some additional file to install in order to compile with
>  Visual Studio Express.
>
>  Anyway, I cannot compile it, due to some errors... some missing c
>  files in the library.
>
>  Where did you find the pre-compiled windows binaries?
>  I searched in the sourceforge web site, but I didn't find them. Just
>  the source, pre-release source and contribs packages.
>
>
>
>  regards,
>  fausto
>
>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>
>  > Hi Fausto,
>  >
>  > I've used the economy package, and I didn't come across that command.
>  > I've added pre-built development (.lib) and runtime (.dll) libraries
>  > to the download page on sourceforge.
>  >
>  > Camiel.
>  >
>  > On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito <fa...@un...> wrote:
>  >> Hello Camiel,
>  >>
>  >>  this is very interesting news...
>  >>  Just a question about POCO libraries: which one we have to compile?
>  >>  the light version, or the enterprise?
>  >>  I'm trying to compile and install the light one, but I have a problem
>  >>  because the visual studio file looks for "mc" command.
>  >>
>  >>  What's that command?
>  >>  Do you have the same problem?
>  >>
>  >>  regards,
>  >>  fausto
>  >>
>  >>
>  >>
>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>  >>
>  >>  > Hello Everyone,
>  >>  >
>  >>  > This e-mail is to inform you that I have just applied a very large
>  >>  > patch to CVS that affects the entire emulator. Over the past few
>  >>  > weeks,. we've run into the limitations of running everything in a
>  >>  > single clock-loop, calling devices' DoClock() functions. This leads to
>  >>  > wildly varying CPU speed, and does not efficiently the processing
>  >>  > power of modern multi-core/multi-processor CPU's.
>  >>  >
>  >>  > The patch that has just been committed gets rid of the DoClock()
>  >>  > functions, and instead lets each device run its own threads as needed.
>  >>  > If you have a dual-core system, the emulated CPU could run on one
>  >>  > core, with the other core taking care of all other devices.
>  >>  >
>  >>  > This is a patch I've been working on for a long time, and it's been a
>  >>  > bit of a pain keeping it in sync with all the other changes that have
>  >>  > happened in the past few weeks, which is why I'm committing it so soon
>  >>  > after the release of 0.19.
>  >>  >
>  >>  > So far the good news, now the bad news:
>  >>  >
>  >>  > This patch is a radical departure from the way we used to do things,
>  >>  > and it breaks a couple of things. The <break> menu on the Serial
>  >>  > console lost it's functionality. IDB doesn't work yet. And, most
>  >>  > importantly, this release probably introduces bugs caused by threads
>  >>  > accessing the same thing at the same time. These issues will all need
>  >>  > to be addressed in the next couple of weeks. Everyone can help out by
>  >>  > submitting bug reports to this list for anything that doesn't work as
>  >>  > expected.
>  >>  >
>  >>  > You will need to install the Poco C++ libraries for the new code
>  >>  to compile.
>  >>  >
>  >>  > The new approach also opens the door to emulating multiple CPU's,
>  >>  > although that is not functional yet. I'm working hard on this, but I'm
>  >>  > missing something in the initialization. The basic bits and pieces are
>  >>  > in place, but the extra cpu's never come fully online. If you think
>  >>  > you can help with this, please contact me.
>  >>  >
>  >>  > I've created a new CVS branch ("no-threading") before this patch that
>  >>  > will be used for necessary bugfixes to the version 0.19 codebase.
>  >>  >
>  >>  > Regards,
>  >>  >
>  >>  > Camiel Vanderhoeven.
>  >>  >
>  >>  > -------------------------------------------------------------------------
>  >>  > This SF.net email is sponsored by: Microsoft
>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  > _______________________________________________
>  >>  > Es40-developers mailing list
>  >>  > Es4...@li...
>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>  >
>  >>
>  >>
>  >>
>  >>  -------------------------------------------------------------------------
>  >>  This SF.net email is sponsored by: Microsoft
>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  _______________________________________________
>  >>  Es40-developers mailing list
>  >>  Es4...@li...
>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>
>  >
>  > -------------------------------------------------------------------------
>  > This SF.net email is sponsored by: Microsoft
>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  > _______________________________________________
>  > Es40-developers mailing list
>  > Es4...@li...
>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Es40-developers mailing list
>  Es4...@li...
>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Fausto S. <fa...@un...>]

Hello Camiel,

updating a little bit the Visual Studio Express project file, I was  
able to compile the poco libraries.
But now the es40 build fails because it doesn't find PocoFoundationmt.lib

I have only Pocofoundation.lib, not MT.

What's this?

A new kind of library?

regards,
fausto

Quoting Camiel Vanderhoeven <iam...@gm...>:

> Hi Fausto,
>
> I compiled them myself. I downloaded the economy package from
> http://pocoproject.org/poco/download/ and built it (both for 32-bit
> windows on my laptop, and for 64-bit windows on my desktop). I have
> the full Visual Studio version, apparently, mc is part of the Windows
> SDK. (That question is in the POCO FAQ:
> http://pocoproject.org/poco/wiki/tiki-view_faq.php?faqId=2#q10).
>
> Camiel.
>
> On Thu, Mar 6, 2008 at 2:05 AM, Fausto Saporito <fa...@un...> wrote:
>> Hi Camiel,
>>
>>  that command is related to Visual Studio (not Express version).
>>  There're some additional file to install in order to compile with
>>  Visual Studio Express.
>>
>>  Anyway, I cannot compile it, due to some errors... some missing c
>>  files in the library.
>>
>>  Where did you find the pre-compiled windows binaries?
>>  I searched in the sourceforge web site, but I didn't find them. Just
>>  the source, pre-release source and contribs packages.
>>
>>
>>
>>  regards,
>>  fausto
>>
>>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>
>>  > Hi Fausto,
>>  >
>>  > I've used the economy package, and I didn't come across that command.
>>  > I've added pre-built development (.lib) and runtime (.dll) libraries
>>  > to the download page on sourceforge.
>>  >
>>  > Camiel.
>>  >
>>  > On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito <fa...@un...> wrote:
>>  >> Hello Camiel,
>>  >>
>>  >>  this is very interesting news...
>>  >>  Just a question about POCO libraries: which one we have to compile?
>>  >>  the light version, or the enterprise?
>>  >>  I'm trying to compile and install the light one, but I have a problem
>>  >>  because the visual studio file looks for "mc" command.
>>  >>
>>  >>  What's that command?
>>  >>  Do you have the same problem?
>>  >>
>>  >>  regards,
>>  >>  fausto
>>  >>
>>  >>
>>  >>
>>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>  >>
>>  >>  > Hello Everyone,
>>  >>  >
>>  >>  > This e-mail is to inform you that I have just applied a very large
>>  >>  > patch to CVS that affects the entire emulator. Over the past few
>>  >>  > weeks,. we've run into the limitations of running everything in a
>>  >>  > single clock-loop, calling devices' DoClock() functions.   
>> This leads to
>>  >>  > wildly varying CPU speed, and does not efficiently the processing
>>  >>  > power of modern multi-core/multi-processor CPU's.
>>  >>  >
>>  >>  > The patch that has just been committed gets rid of the DoClock()
>>  >>  > functions, and instead lets each device run its own threads   
>> as needed.
>>  >>  > If you have a dual-core system, the emulated CPU could run on one
>>  >>  > core, with the other core taking care of all other devices.
>>  >>  >
>>  >>  > This is a patch I've been working on for a long time, and it's been a
>>  >>  > bit of a pain keeping it in sync with all the other changes that have
>>  >>  > happened in the past few weeks, which is why I'm committing   
>> it so soon
>>  >>  > after the release of 0.19.
>>  >>  >
>>  >>  > So far the good news, now the bad news:
>>  >>  >
>>  >>  > This patch is a radical departure from the way we used to do things,
>>  >>  > and it breaks a couple of things. The <break> menu on the Serial
>>  >>  > console lost it's functionality. IDB doesn't work yet. And, most
>>  >>  > importantly, this release probably introduces bugs caused by threads
>>  >>  > accessing the same thing at the same time. These issues will all need
>>  >>  > to be addressed in the next couple of weeks. Everyone can help out by
>>  >>  > submitting bug reports to this list for anything that doesn't work as
>>  >>  > expected.
>>  >>  >
>>  >>  > You will need to install the Poco C++ libraries for the new code
>>  >>  to compile.
>>  >>  >
>>  >>  > The new approach also opens the door to emulating multiple CPU's,
>>  >>  > although that is not functional yet. I'm working hard on   
>> this, but I'm
>>  >>  > missing something in the initialization. The basic bits and   
>> pieces are
>>  >>  > in place, but the extra cpu's never come fully online. If you think
>>  >>  > you can help with this, please contact me.
>>  >>  >
>>  >>  > I've created a new CVS branch ("no-threading") before this patch that
>>  >>  > will be used for necessary bugfixes to the version 0.19 codebase.
>>  >>  >
>>  >>  > Regards,
>>  >>  >
>>  >>  > Camiel Vanderhoeven.
>>  >>  >
>>  >>  >   
>> -------------------------------------------------------------------------
>>  >>  > This SF.net email is sponsored by: Microsoft
>>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  > _______________________________________________
>>  >>  > Es40-developers mailing list
>>  >>  > Es4...@li...
>>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>  >
>>  >>
>>  >>
>>  >>
>>  >>    
>> -------------------------------------------------------------------------
>>  >>  This SF.net email is sponsored by: Microsoft
>>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  _______________________________________________
>>  >>  Es40-developers mailing list
>>  >>  Es4...@li...
>>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>
>>  >
>>  > -------------------------------------------------------------------------
>>  > This SF.net email is sponsored by: Microsoft
>>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  > _______________________________________________
>>  > Es40-developers mailing list
>>  > Es4...@li...
>>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >
>>
>>
>>
>>  -------------------------------------------------------------------------
>>  This SF.net email is sponsored by: Microsoft
>>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  _______________________________________________
>>  Es40-developers mailing list
>>  Es4...@li...
>>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Camiel V. <iam...@gm...>]

Hi Fausto,

There are two settings Release-shared and Release-static when building
Poco. One of them builts PocoFoundation.lib, the other
PocoFoundationmt.lib.

Camiel.

On Thu, Mar 6, 2008 at 12:27 PM, Fausto Saporito <fa...@un...> wrote:
> Hello Camiel,
>
>  updating a little bit the Visual Studio Express project file, I was
>  able to compile the poco libraries.
>  But now the es40 build fails because it doesn't find PocoFoundationmt.lib
>
>  I have only Pocofoundation.lib, not MT.
>
>  What's this?
>
>  A new kind of library?
>
>
>
>  regards,
>  fausto
>
>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>
>  > Hi Fausto,
>  >
>  > I compiled them myself. I downloaded the economy package from
>  > http://pocoproject.org/poco/download/ and built it (both for 32-bit
>  > windows on my laptop, and for 64-bit windows on my desktop). I have
>  > the full Visual Studio version, apparently, mc is part of the Windows
>  > SDK. (That question is in the POCO FAQ:
>  > http://pocoproject.org/poco/wiki/tiki-view_faq.php?faqId=2#q10).
>  >
>  > Camiel.
>  >
>  > On Thu, Mar 6, 2008 at 2:05 AM, Fausto Saporito <fa...@un...> wrote:
>  >> Hi Camiel,
>  >>
>  >>  that command is related to Visual Studio (not Express version).
>  >>  There're some additional file to install in order to compile with
>  >>  Visual Studio Express.
>  >>
>  >>  Anyway, I cannot compile it, due to some errors... some missing c
>  >>  files in the library.
>  >>
>  >>  Where did you find the pre-compiled windows binaries?
>  >>  I searched in the sourceforge web site, but I didn't find them. Just
>  >>  the source, pre-release source and contribs packages.
>  >>
>  >>
>  >>
>  >>  regards,
>  >>  fausto
>  >>
>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>  >>
>  >>  > Hi Fausto,
>  >>  >
>  >>  > I've used the economy package, and I didn't come across that command.
>  >>  > I've added pre-built development (.lib) and runtime (.dll) libraries
>  >>  > to the download page on sourceforge.
>  >>  >
>  >>  > Camiel.
>  >>  >
>  >>  > On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito <fa...@un...> wrote:
>  >>  >> Hello Camiel,
>  >>  >>
>  >>  >>  this is very interesting news...
>  >>  >>  Just a question about POCO libraries: which one we have to compile?
>  >>  >>  the light version, or the enterprise?
>  >>  >>  I'm trying to compile and install the light one, but I have a problem
>  >>  >>  because the visual studio file looks for "mc" command.
>  >>  >>
>  >>  >>  What's that command?
>  >>  >>  Do you have the same problem?
>  >>  >>
>  >>  >>  regards,
>  >>  >>  fausto
>  >>  >>
>  >>  >>
>  >>  >>
>  >>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>  >>  >>
>  >>  >>  > Hello Everyone,
>  >>  >>  >
>  >>  >>  > This e-mail is to inform you that I have just applied a very large
>  >>  >>  > patch to CVS that affects the entire emulator. Over the past few
>  >>  >>  > weeks,. we've run into the limitations of running everything in a
>  >>  >>  > single clock-loop, calling devices' DoClock() functions.
>  >> This leads to
>  >>  >>  > wildly varying CPU speed, and does not efficiently the processing
>  >>  >>  > power of modern multi-core/multi-processor CPU's.
>  >>  >>  >
>  >>  >>  > The patch that has just been committed gets rid of the DoClock()
>  >>  >>  > functions, and instead lets each device run its own threads
>  >> as needed.
>  >>  >>  > If you have a dual-core system, the emulated CPU could run on one
>  >>  >>  > core, with the other core taking care of all other devices.
>  >>  >>  >
>  >>  >>  > This is a patch I've been working on for a long time, and it's been a
>  >>  >>  > bit of a pain keeping it in sync with all the other changes that have
>  >>  >>  > happened in the past few weeks, which is why I'm committing
>  >> it so soon
>  >>  >>  > after the release of 0.19.
>  >>  >>  >
>  >>  >>  > So far the good news, now the bad news:
>  >>  >>  >
>  >>  >>  > This patch is a radical departure from the way we used to do things,
>  >>  >>  > and it breaks a couple of things. The <break> menu on the Serial
>  >>  >>  > console lost it's functionality. IDB doesn't work yet. And, most
>  >>  >>  > importantly, this release probably introduces bugs caused by threads
>  >>  >>  > accessing the same thing at the same time. These issues will all need
>  >>  >>  > to be addressed in the next couple of weeks. Everyone can help out by
>  >>  >>  > submitting bug reports to this list for anything that doesn't work as
>  >>  >>  > expected.
>  >>  >>  >
>  >>  >>  > You will need to install the Poco C++ libraries for the new code
>  >>  >>  to compile.
>  >>  >>  >
>  >>  >>  > The new approach also opens the door to emulating multiple CPU's,
>  >>  >>  > although that is not functional yet. I'm working hard on
>  >> this, but I'm
>  >>  >>  > missing something in the initialization. The basic bits and
>  >> pieces are
>  >>  >>  > in place, but the extra cpu's never come fully online. If you think
>  >>  >>  > you can help with this, please contact me.
>  >>  >>  >
>  >>  >>  > I've created a new CVS branch ("no-threading") before this patch that
>  >>  >>  > will be used for necessary bugfixes to the version 0.19 codebase.
>  >>  >>  >
>  >>  >>  > Regards,
>  >>  >>  >
>  >>  >>  > Camiel Vanderhoeven.
>  >>  >>  >
>  >>  >>  >
>  >> -------------------------------------------------------------------------
>  >>  >>  > This SF.net email is sponsored by: Microsoft
>  >>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  >>  > _______________________________________________
>  >>  >>  > Es40-developers mailing list
>  >>  >>  > Es4...@li...
>  >>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>  >>  >
>  >>  >>
>  >>  >>
>  >>  >>
>  >>  >>
>  >> -------------------------------------------------------------------------
>  >>  >>  This SF.net email is sponsored by: Microsoft
>  >>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  >>  _______________________________________________
>  >>  >>  Es40-developers mailing list
>  >>  >>  Es4...@li...
>  >>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>  >>
>  >>  >
>  >>  > -------------------------------------------------------------------------
>  >>  > This SF.net email is sponsored by: Microsoft
>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  > _______________________________________________
>  >>  > Es40-developers mailing list
>  >>  > Es4...@li...
>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>  >
>  >>
>  >>
>  >>
>  >>  -------------------------------------------------------------------------
>  >>  This SF.net email is sponsored by: Microsoft
>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  >>  _______________________________________________
>  >>  Es40-developers mailing list
>  >>  Es4...@li...
>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >>
>  >
>  > -------------------------------------------------------------------------
>  > This SF.net email is sponsored by: Microsoft
>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  > _______________________________________________
>  > Es40-developers mailing list
>  > Es4...@li...
>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>  >
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Es40-developers mailing list
>  Es4...@li...
>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>

Re: [ES40-developers] ES40 Emulator Status Update

[Fausto S. <fa...@un...>]

Camiel,

I did a check on the Visual Studio Full project files, and I noticed  
the same thing.
Unfortunately the "express" project files don't have the same naming  
convention (and project settings too), and I suppose they use only  
shared version.

Because I was not able to find and install mc.exe, I just rename the  
Pocofoundation.lib in Pocofoundationmt.lib and the es40 build works  
again :-)

regards,
fausto

Quoting Camiel Vanderhoeven <iam...@gm...>:

> Hi Fausto,
>
> There are two settings Release-shared and Release-static when building
> Poco. One of them builts PocoFoundation.lib, the other
> PocoFoundationmt.lib.
>
> Camiel.
>
> On Thu, Mar 6, 2008 at 12:27 PM, Fausto Saporito <fa...@un...> wrote:
>> Hello Camiel,
>>
>>  updating a little bit the Visual Studio Express project file, I was
>>  able to compile the poco libraries.
>>  But now the es40 build fails because it doesn't find PocoFoundationmt.lib
>>
>>  I have only Pocofoundation.lib, not MT.
>>
>>  What's this?
>>
>>  A new kind of library?
>>
>>
>>
>>  regards,
>>  fausto
>>
>>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>
>>  > Hi Fausto,
>>  >
>>  > I compiled them myself. I downloaded the economy package from
>>  > http://pocoproject.org/poco/download/ and built it (both for 32-bit
>>  > windows on my laptop, and for 64-bit windows on my desktop). I have
>>  > the full Visual Studio version, apparently, mc is part of the Windows
>>  > SDK. (That question is in the POCO FAQ:
>>  > http://pocoproject.org/poco/wiki/tiki-view_faq.php?faqId=2#q10).
>>  >
>>  > Camiel.
>>  >
>>  > On Thu, Mar 6, 2008 at 2:05 AM, Fausto Saporito <fa...@un...> wrote:
>>  >> Hi Camiel,
>>  >>
>>  >>  that command is related to Visual Studio (not Express version).
>>  >>  There're some additional file to install in order to compile with
>>  >>  Visual Studio Express.
>>  >>
>>  >>  Anyway, I cannot compile it, due to some errors... some missing c
>>  >>  files in the library.
>>  >>
>>  >>  Where did you find the pre-compiled windows binaries?
>>  >>  I searched in the sourceforge web site, but I didn't find them. Just
>>  >>  the source, pre-release source and contribs packages.
>>  >>
>>  >>
>>  >>
>>  >>  regards,
>>  >>  fausto
>>  >>
>>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>  >>
>>  >>  > Hi Fausto,
>>  >>  >
>>  >>  > I've used the economy package, and I didn't come across that command.
>>  >>  > I've added pre-built development (.lib) and runtime (.dll) libraries
>>  >>  > to the download page on sourceforge.
>>  >>  >
>>  >>  > Camiel.
>>  >>  >
>>  >>  > On Wed, Mar 5, 2008 at 6:18 PM, Fausto Saporito   
>> <fa...@un...> wrote:
>>  >>  >> Hello Camiel,
>>  >>  >>
>>  >>  >>  this is very interesting news...
>>  >>  >>  Just a question about POCO libraries: which one we have to compile?
>>  >>  >>  the light version, or the enterprise?
>>  >>  >>  I'm trying to compile and install the light one, but I   
>> have a problem
>>  >>  >>  because the visual studio file looks for "mc" command.
>>  >>  >>
>>  >>  >>  What's that command?
>>  >>  >>  Do you have the same problem?
>>  >>  >>
>>  >>  >>  regards,
>>  >>  >>  fausto
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>  >>  Quoting Camiel Vanderhoeven <iam...@gm...>:
>>  >>  >>
>>  >>  >>  > Hello Everyone,
>>  >>  >>  >
>>  >>  >>  > This e-mail is to inform you that I have just applied a   
>> very large
>>  >>  >>  > patch to CVS that affects the entire emulator. Over the past few
>>  >>  >>  > weeks,. we've run into the limitations of running everything in a
>>  >>  >>  > single clock-loop, calling devices' DoClock() functions.
>>  >> This leads to
>>  >>  >>  > wildly varying CPU speed, and does not efficiently the processing
>>  >>  >>  > power of modern multi-core/multi-processor CPU's.
>>  >>  >>  >
>>  >>  >>  > The patch that has just been committed gets rid of the DoClock()
>>  >>  >>  > functions, and instead lets each device run its own threads
>>  >> as needed.
>>  >>  >>  > If you have a dual-core system, the emulated CPU could run on one
>>  >>  >>  > core, with the other core taking care of all other devices.
>>  >>  >>  >
>>  >>  >>  > This is a patch I've been working on for a long time,   
>> and it's been a
>>  >>  >>  > bit of a pain keeping it in sync with all the other   
>> changes that have
>>  >>  >>  > happened in the past few weeks, which is why I'm committing
>>  >> it so soon
>>  >>  >>  > after the release of 0.19.
>>  >>  >>  >
>>  >>  >>  > So far the good news, now the bad news:
>>  >>  >>  >
>>  >>  >>  > This patch is a radical departure from the way we used   
>> to do things,
>>  >>  >>  > and it breaks a couple of things. The <break> menu on the Serial
>>  >>  >>  > console lost it's functionality. IDB doesn't work yet. And, most
>>  >>  >>  > importantly, this release probably introduces bugs   
>> caused by threads
>>  >>  >>  > accessing the same thing at the same time. These issues   
>> will all need
>>  >>  >>  > to be addressed in the next couple of weeks. Everyone   
>> can help out by
>>  >>  >>  > submitting bug reports to this list for anything that   
>> doesn't work as
>>  >>  >>  > expected.
>>  >>  >>  >
>>  >>  >>  > You will need to install the Poco C++ libraries for the new code
>>  >>  >>  to compile.
>>  >>  >>  >
>>  >>  >>  > The new approach also opens the door to emulating multiple CPU's,
>>  >>  >>  > although that is not functional yet. I'm working hard on
>>  >> this, but I'm
>>  >>  >>  > missing something in the initialization. The basic bits and
>>  >> pieces are
>>  >>  >>  > in place, but the extra cpu's never come fully online.   
>> If you think
>>  >>  >>  > you can help with this, please contact me.
>>  >>  >>  >
>>  >>  >>  > I've created a new CVS branch ("no-threading") before   
>> this patch that
>>  >>  >>  > will be used for necessary bugfixes to the version 0.19 codebase.
>>  >>  >>  >
>>  >>  >>  > Regards,
>>  >>  >>  >
>>  >>  >>  > Camiel Vanderhoeven.
>>  >>  >>  >
>>  >>  >>  >
>>  >>   
>> -------------------------------------------------------------------------
>>  >>  >>  > This SF.net email is sponsored by: Microsoft
>>  >>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  >>  > _______________________________________________
>>  >>  >>  > Es40-developers mailing list
>>  >>  >>  > Es4...@li...
>>  >>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>  >>  >
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>   
>> -------------------------------------------------------------------------
>>  >>  >>  This SF.net email is sponsored by: Microsoft
>>  >>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  >>  _______________________________________________
>>  >>  >>  Es40-developers mailing list
>>  >>  >>  Es4...@li...
>>  >>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>  >>
>>  >>  >
>>  >>  >   
>> -------------------------------------------------------------------------
>>  >>  > This SF.net email is sponsored by: Microsoft
>>  >>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  > _______________________________________________
>>  >>  > Es40-developers mailing list
>>  >>  > Es4...@li...
>>  >>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>  >
>>  >>
>>  >>
>>  >>
>>  >>    
>> -------------------------------------------------------------------------
>>  >>  This SF.net email is sponsored by: Microsoft
>>  >>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  >>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  >>  _______________________________________________
>>  >>  Es40-developers mailing list
>>  >>  Es4...@li...
>>  >>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >>
>>  >
>>  > -------------------------------------------------------------------------
>>  > This SF.net email is sponsored by: Microsoft
>>  > Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  > _______________________________________________
>>  > Es40-developers mailing list
>>  > Es4...@li...
>>  > https://lists.sourceforge.net/lists/listinfo/es40-developers
>>  >
>>
>>
>>
>>  -------------------------------------------------------------------------
>>  This SF.net email is sponsored by: Microsoft
>>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>  _______________________________________________
>>  Es40-developers mailing list
>>  Es4...@li...
>>  https://lists.sourceforge.net/lists/listinfo/es40-developers
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Es40-developers mailing list
> Es4...@li...
> https://lists.sourceforge.net/lists/listinfo/es40-developers
>