Thread overview | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
February 21, 2013 Build problems | ||||
---|---|---|---|---|
| ||||
I have downloaded the zip files, but have not run the git command. (No git on this machine, which is win 7, 64) $ rdmd build base swt (in ...\dwt) Building dwt-base workdir=>...\dwt\base\src dmd.exe @...dwt\rsp lib.exe @...dwt\rsp > ...dwt\olog.txt Building org.eclipse.swt.win32.win32.x86 workdir=>...\dwt\org.eclipse.swt.win32.win32.x86\src dmd.exe @...\dwt\rsp ...dwt\imp\java\lang\util.di(385): Error: opCall cannot be interpreted at compile time, because it has no available source code --- same error message again --- org\eclipse\swt\internal\Compatibility.d(382): Error: template instance java.lang.util.getImportData!("org.eclipse.swt.internal.SWTMessages.properties") error instantiating The same last two error messages are repeated until "org.eclipse.swt.internal.SWTMessages_hu.properties" and results in object.Exception@build.d(243): compile error |
February 21, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to deed | On 2013-02-21 19:12, deed wrote: > I have downloaded the zip files, but have not run the git command. (No > git on this machine, which is win 7, 64) > > $ rdmd build base swt > (in ...\dwt) > Building dwt-base > workdir=>...\dwt\base\src > dmd.exe @...dwt\rsp > lib.exe @...dwt\rsp > ...dwt\olog.txt > Building org.eclipse.swt.win32.win32.x86 > workdir=>...\dwt\org.eclipse.swt.win32.win32.x86\src > dmd.exe @...\dwt\rsp > ...dwt\imp\java\lang\util.di(385): Error: opCall cannot be interpreted > at compile time, because it has no available source code > --- same error message again --- > org\eclipse\swt\internal\Compatibility.d(382): Error: template instance > java.lang.util.getImportData!("org.eclipse.swt.internal.SWTMessages.properties") > error instantiating > > The same last two error messages are repeated until > "org.eclipse.swt.internal.SWTMessages_hu.properties" > and results in > object.Exception@build.d(243): compile error Seems like a missing -J flag. It should point to this folder, on the local machine: https://github.com/d-widget-toolkit/org.eclipse.swt.win32.win32.x86/tree/master/res -- /Jacob Carlborg |
February 21, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | > Seems like a missing -J flag. It should point to this folder, on the local machine: https://github.com/d-widget-toolkit/org.eclipse.swt.win32.win32.x86/tree/master/res
Tried to rebuild on another computer and it worked fine, so will recheck the rsp file. Thanks for your help so far.
|
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | Hello,
I don't understand how is it that it works on one computer and doesn't work on other including mine?
To me it looks like compile error. Thus not like something cannot be found. Anyway I will try to include, or check mentioned -J flag.
Dňa 21. 2. 2013 22:30 Jacob Carlborg wrote / napísal(a):
> On 2013-02-21 19:12, deed wrote:
>> I have downloaded the zip files, but have not run the git command. (No
>> git on this machine, which is win 7, 64)
>>
>> $ rdmd build base swt
>> (in ...\dwt)
>> Building dwt-base
>> workdir=>...\dwt\base\src
>> dmd.exe @...dwt\rsp
>> lib.exe @...dwt\rsp > ...dwt\olog.txt
>> Building org.eclipse.swt.win32.win32.x86
>> workdir=>...\dwt\org.eclipse.swt.win32.win32.x86\src
>> dmd.exe @...\dwt\rsp
>> ...dwt\imp\java\lang\util.di(385): Error: opCall cannot be interpreted
>> at compile time, because it has no available source code
>> --- same error message again ---
>> org\eclipse\swt\internal\Compatibility.d(382): Error: template instance
>> java.lang.util.getImportData!("org.eclipse.swt.internal.SWTMessages.properties")
>>
>> error instantiating
>>
>> The same last two error messages are repeated until
>> "org.eclipse.swt.internal.SWTMessages_hu.properties"
>> and results in
>> object.Exception@build.d(243): compile error
>
> Seems like a missing -J flag. It should point to this folder, on the
> local machine:
> https://github.com/d-widget-toolkit/org.eclipse.swt.win32.win32.x86/tree/master/res
>
>
|
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | There seems to be an -J flag:
-JC:\vcs\dlang\dwt\res
It is however not the folder you mentioned. So does this mean that the second -J could be added, or this one changed?
Interestingly I tried the command
dmd @rsp
And it issued errors like cannod read ...\ACC.d. It however seems that import path is set in generated rsp...
Dňa 21. 2. 2013 22:30 Jacob Carlborg wrote / napísal(a):
> On 2013-02-21 19:12, deed wrote:
>> I have downloaded the zip files, but have not run the git command. (No
>> git on this machine, which is win 7, 64)
>>
>> $ rdmd build base swt
>> (in ...\dwt)
>> Building dwt-base
>> workdir=>...\dwt\base\src
>> dmd.exe @...dwt\rsp
>> lib.exe @...dwt\rsp > ...dwt\olog.txt
>> Building org.eclipse.swt.win32.win32.x86
>> workdir=>...\dwt\org.eclipse.swt.win32.win32.x86\src
>> dmd.exe @...\dwt\rsp
>> ...dwt\imp\java\lang\util.di(385): Error: opCall cannot be interpreted
>> at compile time, because it has no available source code
>> --- same error message again ---
>> org\eclipse\swt\internal\Compatibility.d(382): Error: template instance
>> java.lang.util.getImportData!("org.eclipse.swt.internal.SWTMessages.properties")
>>
>> error instantiating
>>
>> The same last two error messages are repeated until
>> "org.eclipse.swt.internal.SWTMessages_hu.properties"
>> and results in
>> object.Exception@build.d(243): compile error
>
> Seems like a missing -J flag. It should point to this folder, on the
> local machine:
> https://github.com/d-widget-toolkit/org.eclipse.swt.win32.win32.x86/tree/master/res
>
>
|
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Lubos Pintes | I am back on the first computer and the exact same thing doesn't work. The rsp file points to ...dwt\res, not ...\dwt\org.eclipse.swt.win32.win32.x86\res, but anyway, the files seem to be similar. Also, saving the generated rsp file with updated paths and run $ dmd @rsp gives the exact same result. Replacing util.di with util.d (as mentioned in another thread) gives the same result. Could there be anything luring in the background blocking the attempted instantiations? Any settings in Windows that should be changed? |
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to deed | Actually if I properly understood the build.d, the resources are copied to ...\res. So the -J flag probably points to correct files.
Just did a diff on both dirs i.e. res and ...\win32\res, and only difference are some images.
Dňa 22. 2. 2013 11:07 deed wrote / napísal(a):
> I am back on the first computer and the exact same thing doesn't work.
> The rsp file points to ...dwt\res, not
> ...\dwt\org.eclipse.swt.win32.win32.x86\res, but anyway, the files seem
> to be similar. Also, saving the generated rsp file with updated paths
> and run $ dmd @rsp gives the exact same result. Replacing util.di with
> util.d (as mentioned in another thread) gives the same result.
>
> Could there be anything luring in the background blocking the attempted
> instantiations? Any settings in Windows that should be changed?
|
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Lubos Pintes | On 2013-02-22 10:07, Lubos Pintes wrote: > Hello, > I don't understand how is it that it works on one computer and doesn't > work on other including mine? > To me it looks like compile error. Thus not like something cannot be > found. Anyway I will try to include, or check mentioned -J flag. I'll give it a try and compile it myself, probably during this weekend. I'm usually not using Windows. -- /Jacob Carlborg |
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to deed | 22.02.2013 17:07, deed пишет: > Replacing util.di with > util.d (as mentioned in another thread) gives the same result. I read about replacing, but nevertheless - did you remove util.di or place util.d alongit? this is my way to build DWT on win7 using dmd 2.062 (it's dirty, but works for me) cd path\to\dwt dmd build.d build dwt now we have dwt-base.lib in .\lib del .\imp\java\lang\util.di copy .\base\src\java\lang\util.d .\imp\java\lang\ build swt now we have other libraries in .\lib but it is not the end: del .\imp\org\eclipse\swt\internal\Library.di copy .\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\Library.d .\imp\org\eclipse\swt\internal now it works for me. hope it helps before building will be fixed in normal way. I have no time now to do it myself. |
February 22, 2013 Re: Build problems | ||||
---|---|---|---|---|
| ||||
Posted in reply to Alexandr Druzhinin | Yes it works. Only the first command you mentioned is
build base
I made a batch script based on your description, thank you.
Dňa 22. 2. 2013 11:36 Alexandr Druzhinin wrote / napísal(a):
> 22.02.2013 17:07, deed пишет:
>> Replacing util.di with
>> util.d (as mentioned in another thread) gives the same result.
>
> I read about replacing, but nevertheless - did you remove util.di or
> place util.d alongit?
>
>
> this is my way to build DWT on win7 using dmd 2.062 (it's dirty, but
> works for me)
>
> cd path\to\dwt
> dmd build.d
> build dwt
>
> now we have dwt-base.lib in .\lib
>
> del .\imp\java\lang\util.di
> copy .\base\src\java\lang\util.d .\imp\java\lang\
> build swt
>
> now we have other libraries in .\lib
>
> but it is not the end:
> del .\imp\org\eclipse\swt\internal\Library.di
> copy
> .\org.eclipse.swt.win32.win32.x86\src\org\eclipse\swt\internal\Library.d
> .\imp\org\eclipse\swt\internal
>
> now it works for me. hope it helps before building will be fixed in
> normal way. I have no time now to do it myself.
|
Copyright © 1999-2021 by the D Language Foundation