Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4F7F9C70 for ; Fri, 11 May 2012 08:35:53 +0000 (UTC) Received: (qmail 63779 invoked by uid 500); 11 May 2012 08:35:53 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 63704 invoked by uid 500); 11 May 2012 08:35:52 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 63687 invoked by uid 99); 11 May 2012 08:35:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 08:35:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [87.253.162.5] (HELO server5.configcenter.info) (87.253.162.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 08:35:43 +0000 Received: from [9.155.132.107] (deibp9eh1--blueice3n2.emea.ibm.com [195.212.29.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: web445p1) by server5.configcenter.info (Postfix) with ESMTP id 404401BB09F4 for ; Fri, 11 May 2012 10:35:19 +0200 (CEST) Message-ID: <4FACCF44.3080601@a-w-f.de> Date: Fri, 11 May 2012 10:35:16 +0200 From: Andre Fischer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Which program process scp2? References: In-Reply-To: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (server5.configcenter.info [0.0.0.0]); Fri, 11 May 2012 10:35:19 +0200 (CEST) X-server5-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 404401BB09F4.A3FDA X-server5-MailScanner: Found to be clean X-server5-MailScanner-From: af@a-w-f.de X-Old-Spam-Status: No On 11.05.2012 10:01, laser laser wrote: > Hello my friend: > > I have a question to ask. > Included in the new packaging process are different Perl programs, that create the native installation sets based on the information stored in our platform independent installation set description language ?scp��. Files, directories, and many things more are described in the cvs module ?scp2��. Based on these files, a platform and product specific setup script is created, which is then used by the new packaging process to create the native installation sets. The different processes are shown in the following graphic: > > preprocessor > scp file------------------------------------------->pre file > | > | > | perl file formatting > | > perl-Linker | > setup script--------------------------------------- par file > | > perl- | > Packer | > | windows > |---------------------------------------------> Windows Installation set > | NoN-Windows > |--------------------epm-------------------->RPM, Solaris package,... > > > My question Which program process scp2 files ? The resulting file ��setup script��in there? > At the moment I can give only a partial answer because I am setting up a new machine and do not have access to my development files. Here is what I have found out so far: Creation of .par files from .scp files is triggered by makefiles in main/scp2/source. The rules can be found in main/solenv/inc/pstrules.mk. A par file is first pre-processed by cpp.lcc into a .pre file. The .pre files are then transformed into the .par files by scpcomp. -Andre > In windows > How according to "setup script" Generate the windows installation set?