Re: [tools-dev] --with-xxxx-path parameters does not work for configure script on Windows
On 9/6/05, Volker Quetschke [EMAIL PROTECTED] wrote: Hi Jeongkyu, For building OO.o 2.0 on Windows, I tried to set following parameters but the paths don't count in configure script (I tried both long format and 8.3 format). --with-mspdb-path --with-midl-path --with-csc-path --with-nsis-path Is this my own problem or known issue? No, works just fine. If you tell us what you did, we could tell you what to change. This might be only for me but I was confused by configure output. Without setting for mspdb path, configure stopped. With correct --with-mspdb-path, it passed with message, 'checking the Microsoft C/C++ Compiler... checking for mspdb71.dll... no found (/cygdrive/c/PROGRA~1/MICROS~2.NET/Vc7/bin/cl.exe)' . Without setting for csc path, configure stopped. With correct --with-csc-path, it passed with message, 'checking for csc.exe... no' . Without setting for nsis path, there was a warning at the end of output. With correct --with-nsis-path, it passed with message, 'checking for NSIS... checking for nsis.exe... no found (/cygdrive/c/PROGRA~1/NSIS)' . However, configure did not stopped without midl setting. And I tried both --with-midl-path=/cygdrive/c/Program Files/Microsoft Visual Studio .NET 2003/Common7/Tools/bin and --with-midl-path=/cygdrive/c/Program Files/Microsoft Visual Studio .NET 2003/Common7/Tools but still I got a message, 'checking for midl.exe... no'. Thus I could not confirm midl path was correctly set. And --with-cl-home was little bit tricky because I had to set /cygdrive/c/Program Files/Microsoft Visual Studio .NET 2003/Vc7 instead of /cygdrive/c/Program Files/Microsoft Visual Studio .NET 2003/Vc7/bin which has cl.exe. For now, I am going to stick with PATH variable method which gives me more comfortable output. :-) Jeongkyu -- Jeongkyu Kim OpenOffice.org Korean community lead Official website http://ko.openoffice.org Community forum http://oooko.net/ Personal bloghttp://oooko.net/gomme - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] build tool with html build status page
Hi, David Fraser wrote: Vladimir Glazounov wrote: Hi all, from now on the the new feature in build tool is available. You can see the status of the build in Technicolor on a generated html page. Just resync your solenv/bin/build.pl to the version of SRC680 m128 and enjoy! (Trigger with '--html', help available) Best regards, Vladimir PS: I'm looking for enhancement proposals comments. This is fantastic! I used to have a shell script that attempted to do a similar thing by watching output logs but this approach is much better... Can you make dmake do this or do you have to run it via build.pl? the feature is in build.pl only Cheers, Ivo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] --with-xxxx-path parameters does not work for configure script on Windows
On 9/7/05, Volker Quetschke [EMAIL PROTECTED] wrote: See above. It would fail if midl.exe would be missing. You're correct. There might be an mistake in my previous test. :-) Jeongkyu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] build tool with html build status page
From: Ivo Hinkelmann [EMAIL PROTECTED] Date: Wed, 07 Sep 2005 15:33:07 +0200 Can you make dmake do this or do you have to run it via build.pl? the feature is in build.pl only ... and instead of dmake in top-level directory, you can use cd instsetoo_native build --all --html -- Pavel Janík Replace repetitive expressions by calls to a common function. -- The Elements of Programming Style (Kernighan Plaugher) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] build tool with html build status page
Pavel Janík wrote: From: Ivo Hinkelmann [EMAIL PROTECTED] Date: Wed, 07 Sep 2005 15:33:07 +0200 Can you make dmake do this or do you have to run it via build.pl? the feature is in build.pl only ... and instead of dmake in top-level directory, you can use cd instsetoo_native build --all --html That's what I wanted to know, thanks! David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [tools-dev] Code analysis tool
Dear All I am Mohammed Mamdouh , working with Ramez on the OOQ project, we are still waiting for your support and comments, as filling for ramez, The tool will produce xmi file from the code also which is readable by ARGOUML and possibly Borland Together or Rational rose your concern will be very appreciated Best Ragerds Mohammed From: Ramez Gabriel [EMAIL PROTECTED] Reply-To: dev@tools.openoffice.org To: dev@tools.openoffice.org Subject: [tools-dev] Code analysis tool Date: Sat, 03 Sep 2005 14:22:58 + Dear all first I have to introduce myself, I am a member of the Egyptian team working on the code analysis tool, we contacted Mr.Christof pintaske and Mr.Martin HollMichel and other members who were a lot of help to us , we finalized the design and went far enough in the implementation, Mr.Martin redirected us to the mailing group to ask for the developers opinion about the tool, the first release will be delivered soon as a prototype will be available before 20/9/2005 for evaluation we are first asking for your opinions about the tool and how it's evaluation will be organized, the first release will be on testing the design of the source code from any supported language (mainly JAVA, C++ and more hopefuly) the next points will be exactly what this tool will automatically check : Class size: The number of attributes in a class. The number of operations in a class. The number of public operations in a class. For inner classes, nesting level of the inner class Class Inheritance: The number of interfaces the class implements (UML Abstraction). The number of children of the class (UML Generalization). The number of descendants of the class (UML Generalization). The number of ancestors of the class. The depth of the class in the inheritance hierarchy. Class to leaf depth. The number of inherited operations. The number of inherited attributes. Class Coupling: The number of dependencies where the class is the client. The number of dependencies where the class is the supplier. The number of associated classes in the same scope. The number of associated classes in the same scope branch. The number of associated classes not in the same scope branch. The number of times the class is externally used as attribute type. The number of attributes in the class having an interface or class as their type. The number of object instances of the class in the model. The number of classifier roles where the class is the base. Package Size: The number of classes in the package. The number of interfaces in the package. Nesting level of the package in the package hierarchy. Package Coupling: The number of packages on which classes of this package depend. The number of elements outside the package having an association with a class inside the package. Interface Metrics: The number of operations in the interface. The number of times the interface is used as attribute type. The number of associations the interface participates in. The number of classes directly implementing the interface (UML Abstraction). The number of classes implementing a descendent of the interface. The number of ancestors of the interface. The number of descendants of the interface. Diagram-specific Metrics: The number of classes on the diagram. The number of interfaces on the diagram. The number of packages on the diagram. The number of associations on the diagram. The number of generalizations on the diagram. The number of abstractions on the diagram. thanks for your patience and we are sorry for the long mail but we are waiting for the comments and support of anyone interested your concern will be highly appreciated best regards Ramez gabriel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
