I guys,
I've done a successful build on windows just to test... It went fine (after
a hard fight ;-))
Now I've changed some things on the autogen (for instance change languages
from "en-US pt" to just "en-US") and re-run it and also changed the product
name on "*instsetoo_native/util/openoffice.lst*" and now everytime it gets
to the tail_buil if fails doing the extensions in the OXT... it fails in
every extension with this:
[ build OXT ] report-builder
S=C:/libre362 && O=$S/solver/wntmsci12.pro &&
W=$S/workdir/wntmsci12.pro&&  mkdir -p
$W/Extension/report-builder/root/META-INF
$W/Extension/report-builder/root/registration &&  cp -f
$W/Extension/report-builder/description.xml
$W/Extension/report-builder/root/description.xml &&  cp -f
$S/reportbuilder/util/manifest.xml
$W/Extension/report-builder/root/META-INF/manifest.xml && cp -f
$O/bin/osl/license.txt $W/Extension/report-builder/root/registration && cp
$W/Extension/report-builder/root && cd $W/Extension/report-builder/root &&
zip  -rX --filesync $W/Extension/report-builder.oxt META-INF
THIRDPARTYREADMELICENSE.html commons-logging-1.1.1.jar components.rdb
description-en-US.txt description.xml flow-engine-0.9.4.jar flute-1.1.6.jar
images/extension_32.png libbase-1.1.6.jar libfonts-1.1.6.jar
libformula-1.1.7.jar liblayout-0.2.10.jar libloader-1.1.6.jar
librepository-1.1.6.jar libserializer-1.1.6.jar libxml-1.1.7.jar
readme_en-US.html readme_en-US.txt registration
registry/data/org/openoffice/Office/Accelerators.xcu
registry/data/org/openoffice/Office/DataAccess.xcu
registry/data/org/openoffice/Office/Embedding.xcu
registry/data/org/openoffice/Office/ExtendedColorScheme.xcu
registry/data/org/openoffice/Office/Paths.xcu
registry/data/org/openoffice/Office/ReportDesign.xcu
registry/data/org/openoffice/Office/UI/Controller.xcu
registry/data/org/openoffice/Office/UI/DbReportWindowState.xcu
registry/data/org/openoffice/Office/UI/ReportCommands.xcu
registry/data/org/openoffice/Setup.xcu
registry/data/org/openoffice/TypeDetection/Filter.xcu
registry/data/org/openoffice/TypeDetection/Types.xcu
registry/schema/org/openoffice/Office/ReportDesign.xcs
registry/schema/org/openoffice/Office/UI/DbReportWindowState.xcs
registry/schema/org/openoffice/Office/UI/ReportCommands.xcs
reportbuilderwizard.jar sac.jar sun-report-builder.jar
template/en-US/wizard/report/default.otr
cp: missing destination file operand after `C:/libre362/workdir/
wntmsci12.pro/Extension/report-builder/root'
Try `cp --help' for more information.
make[2]: *** [C:/libre362/workdir/wntmsci12.pro/Extension/report-builder.oxt]
Error 1
make[2]: Leaving directory `/cygdrive/c/libre362/tail_build'
Basically it seems that in the command:
"cp  $W/Extension/report-builder/root"
 it's missing the first operand....
Can someone help me finding what's worng.. is there some environment
variable that went missing? Where dows this "cp" command line commes from
so that I can try to see what should be there (I didn't found it)?
Thanks a lot
-- 
*Flávio Moringa*
Project Leader
Caixa Mágica Software
Energia Open Source
Rua Soeiro Pereira Gomes, Lote 1 - 4.º B,
Edifício Espanha, 1600-196 Lisboa - Portugal
Tel.: +351 217 921 260 Fax: +351 217 921 261
http://www.caixamagica.pt
https://twitter.com/flaviomoringa
https://www.facebook.com/flaviomoringa<https://www.facebook.com/flavio.moringa>
http://pt.linkedin.com/in/flaviomoringa
http://people.caixamagica.pt/flaviomoringa
Context
- Error on rebuild in Windows "cp: missing destination file operand	after" · Flavio Moringa
 
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.