Well, you are fast in answering. I just wanted to change the bugreport...
OK, I figured that out so far.
The real problem I had was in the nmake test.It did fail for most of the
tests, so I was a bit wary on using the module.
After fixing it by adding the -u <somedb> to the start command in sub
_start in cmsynergy.pm most tests succeed. I do not have a filled
tutorial testdb at hand, so that is why others fail.
After having brought the tool up so far, I was convinced of its use and
tried to use the module. And indeed, when specifying the ui_database_dit
==> 'somedb' it works fine.!
So my problem crystals out to be: cannot nmake test on winxp systems.
What I saw furthermore was that at the end of the nmake the summary was
awkward: more tests fail then the total shows:
"
-------------------------------------------------------------------------------
t\03query.t 255 65280 24 26 108.33% 10-24
t\04finduse.t 255 65280 6 7 116.67% 3-6
t\05history.t 255 65280 10 16 160.00% 3-10
t\06misc.t 255 65280 18 20 111.11% 9-18
t\07workarea.t 255 65280 45 84 186.67% 4-45
t\11relations.t 255 65280 11 16 145.45% 4-11
t\12project.t 255 65280 16 26 162.50% 4-16
t\90examples.t 4 1024 8 4 50.00% 4-5 7-8
2 tests and 26 subtests skipped.
Failed 8/17 test scripts, 52.94% okay. 104/401 subtests failed, 74.06%
okay.
NMAKE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0xff'
Stop.
"
Only test 9 seems to be correct in summarizing.
regards and thanks for your rapid answer,
Raymond
Show quoted text ----- Original Message -----
From: " via RT"
To: rroo@mail.com
Subject: [rt.cpan.org #27260] Cannot start session under winxp
Date: Wed, 23 May 2007 08:11:51 -0400
On Wed May 23 07:15:09 2007, rroo wrote:
> The windows interface needs the -u option at the ccm start command.
Only
> if the database is not accessible from this host.
That's what the optional
-ui_database_dir => "/some/path"
for VCS::CMSynergy->new(...) is for
(gets translated to "ccm start -u /some/path ...").
You may have been bitten by this if you started a Synergy session
before (w/o VCS::CMSynergy) and supplied the ui_dir when prompted.
Then Synergy enters your setting into your personal ccm.ini file and
all future sessions will default it from there. However,
VCS::CMSynergy
prevents Synergy from reading your personal ccm.ini (only the
global ccm.ini in $CCM_HOME/etc is sourced). The reason is that
I don't want scripts to sometimes work and sometimes not,
depending on random stuff in your personal ccm.ini.
If you _do_ want do have a ccm.ini sourced, use
-ini_file => "/path/to/ccm.ini"
for VCS::CMSynergy->new.
Cheers, Roderich
