Re: Including modified SNTP component in the Release

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The timesvc_ALL.lib is a product of the way that the sysgen works. What you
need to do then is to make sure these are set in your sources file

WINCEPROJ=servers
WINCETREE=servers (this one I'm not as sure about, so if you run into issues
remove it).

Usually they're not needed in a given sources but when you fork code off you
may need to set them.

Then after build, from a command line window <sysgen -p servers timesvc>.
This should get you the dll, check out \<winceroot>\build.log to see if
anything went wrong and if the DLL doesn't get output to your
releasedirectory.

Sorry I'm not more confident about the steps here, I don't have a lot of
experience in forking code like this.

--
John Spaith
Development Lead, Windows CE
Microsoft Corporation

Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.

"adolf123" <adolf123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6B2747A-150B-4DD8-9340-71ED5D809303@xxxxxxxxxxxxxxxx
I will clarify on the way I have tried to implement this. I have created a
SOURCES project by duplicating the SNTP directory available under the
WINCE
ROOT\private\servers\timesvc2 directory. This project has the same target
name (tsvc_sntp.lib) as the original. After some investigations, I found
that
the tsvc_sntp.lib is used to generate another intermediate library
timesvc_ALL.lib and timesvc.dll is generated from this. I think the simple
solution for me would be to modify the SOURCES file for the
timesvc_ALL.lib.
Can anyone let mw know the location of this file?

thanks in advance,


"John Spaith [MS]" wrote:

A few possibilities - if you're in command line build you need WINCEREL=1
env variable or else the binary won't get copied. Also it's possible the
sysgen isn't taking for some reason - what command exactly did you run to
make that happen? For me developing timesv, it's <sysgen -p servers
timesvc> but I don't know how you cloning the files may have changed
things.
Just running 'sysgen' by itself won't make DLL get rebuilt if that's what
you were trying.

Another hint is to look at \WinceRoot\build.log and
<yourProjectDir>\build.log, they may contain extra clues to what's up
here.

--
John Spaith
Development Lead, Windows CE
Microsoft Corporation

Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All
rights
reserved.

"adolf123" <adolf123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:68E5651C-BD4C-444F-A975-C2222947F382@xxxxxxxxxxxxxxxx
hello,

I am quite new to WinCE and PB, so this may be a silly question, am not
too
sure. I have modified a file (sntp.cxx) used to build the timesvc DLL.
I
have
done this using the following steps:

1> Created a SOURCES project 'sntp' (same name as the original
project).
2> Copied the necessary files (.h, .cxx) to the new directory and made
the
necessary modifications in the files.
3> Specifed the same target name (tsvc_sntp.lib), which is the
intermediate
file for building the DLL. Added the necessary INCLUDE paths.
4> Did a Sysgen.
5> Built the new modified component project.

However, when I see the final Release directory, the timesvc.dll file
is
the
old one, with the same timestamp. Can someone please tell me if I am
doing
something wrong here?

I think I may have missed some crucial step in between. I am not sure
how
to
instruct PB to use my modified file instead of the original one to
build
timesvc.dll. Any help is valued.

thanks in advance,





.

Relevant Pages

  • Re: timesvc problem synchronizing time
    ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ... packets being sent when CE does the timesvc request would also be helpful. ... After timesvc has get the time from the server, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: timesvc problem synchronizing time
    ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ... packets being sent when CE does the timesvc request would also be helpful. ... After timesvc has get the time from the server, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Including modified SNTP component in the Release
    ... A few possibilities - if you're in command line build you need WINCEREL=1 ... This posting is provided "AS IS" with no warranties, and confers no rights. ... I have modified a file used to build the timesvc DLL. ...
    (microsoft.public.windowsce.embedded)
  • Re: NTP time synch on CE 5.0
    ... SNTP component. ... Also note that timesvc.dll is a big-time modularized DLL - it can in theory ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ...
    (microsoft.public.windowsce.embedded)
  • RE: Re-Enabling HTTP Compression after applying paranoid security settings to IIS/W2K
    ... You may want to try reregistering ... This posting is provided "AS IS" with no warranties, and confers no rights. ... © 2001 Microsoft Corporation. ...
    (microsoft.public.inetserver.iis.security)