Re: dmake issue

Many thanks, Volker.
I'll bring down 116 and start over.
In the meantime, I already reinstalled the dmake directory, so that may 
or may not be an issue.

Let me try 116 before I return with any questions.

Thanks again!
Jack

Volker Quetschke wrote:

> [email protected] wrote:
> 
>> Here is what I did. I'll show the configure line, then show
>> a couple of results. If you really need to see the output
>> of configure, it's huge, but I can send it along either in
>> an email or zipped and attached.
> 
> It's beter to create an issue than posting it to the mailing
> list.
> 
> 
>> Running Configure:
>>
>> $ ./configure --with-cl-home="/cygdrive/c/Program
>> Files/Microsoft Visual Studio
>>  .NET 2003/Vc7"
>> --with-csc-path="/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v1
>> .1.4322" --with-frame-home="/cygdrive/c/Program
>> Files/Microsoft Visual Studio .
>> NET 2003/SDK/v1.1" --with-psdk-home="/cygdrive/c/Program
>> Files/Microsoft Platfo
>> rm SDK" --with-mspdb-path="/cygdrive/c/Program
>> Files/Microsoft Visual Studio .N
>> ET 2003/Common7/IDE" --with-midl-path="/cygdrive/c/Program
>> Files/Microsoft Visu
>> al Studio .NET 2003/Common7/Tools/Bin" --with-java
>> --with-jdk-home="/cygdrive/c
>> /j2sdk1.4.2_08"
>>  --with-ant-home="/cygdrive/c/downloads/ant/apache-ant-1.6.2"
>> -
>> disable-directx --with-use-shell=tcsh
>>
>> Configure said there were warnings. The only warning in the
>> warn file was that
>> NSIS not found, no self contained installer will be build.
> 
> Yes, that warning is OK. You will not get the self-contained
> installer at the end, but that's all.
> 
>> There is a statement I don't understand also in the
>> configure result:
>>
>> * USAGE:
>> * Source winenv.set (in tcsh) or winenv.set.sh (in sh)
>> * in order to set up the build-environment variables.
>>
>> But there is no mention of that at
>> http://tools.openoffice.org/dev_docs/build_windows_tcsh.html
> 
> I doubt that, I see the following in that link:
> 
> 
> tcsh - Example
> Even though tcsh is the default shell since m83, you should enable the
> use of tcsh with --with-use-shell=tcsh.
> 
> To run the configure script, type the following command:
> 
> $SRC_ROOT> cd config_office
> config_office> ./configure
> --with-cl-home="/cygdrive/c/Programme/Microsoft Visual Studio .NET 
> 2003/Vc7"
> --with-jdk-home=/cygdrive/c/j2sdk1.4.1_02 --with-use-shell=tcsh
> 
> There are a number of options that you can use with the configure
> script. To display these options, type the following command:
> 
> config_office> ./configure --help
> 
> After running configure, you have to continue in a tcsh shell:
> 
> $SRC_ROOT> tcsh
> 
> To create the dmake make utility that is needed for the build of
> OpenOffice.org type the following command:
> 
> $SRC_ROOT> ./bootstrap
> 
> Now source the configuration file which sets all environment variables:
> 
> $SRC_ROOT> source winenv.set
> 
> Don't forget to run
> 
> $SRC_ROOT> rehash
> 
> afterwards.
> 
> 
>> So I went to the next step: jumping into tcsh:
>>
>> $ tcsh
>> Badly placed ()'s.
> 
> That's strange. I guess you have to debug that as it works
> fine for me. Propably one of your startup files is messed up.
> Btw. which version of cygwin/tcsh are you using?
> 
>> Googling that error message got me nowhere so I ignored
>> that. The next step is bootstrap. Change directory and:
>>
>>
>>> ./bootstrap
>>
>>
>> cp: cannot stat
>> `/cygdrive/c/downloads/openOffice/sdk1.9.109/SRC680_m109/dmake/d
>> make.exe': No such file or directory
> 
> Is this all you get after the ./bootstrap command?
> Delete your dmake directory and unpack it from scratch.
> 
>> That is where we leave it. I cannot get past that error.
>> There really is no dmake.exe in the source drop. This, btw,
>> is 680_m109 -- I'm aware there is a 114 out there but I
>> haven't found the source drop for it yet.
> 
> <http://www.openoffice.org/dev_docs/source/get_source.html>
> and you can use m116. (Branch SRC680_m116)
> 
>> If I get past that, then I'm off to do something about
>> rehash. Not sure what that means. For now, I'd like to get
>> dmake working.
> 
> Hint: "man tcsh" and search for rehash if you really want to
> know the details.
> 
> 
> Volker
>