On Tue, Jul 31, 2012 at 5:42 PM, Andrew Fish <[email protected]> wrote:
>
> On Jul 31, 2012, at 5:29 PM, Melwyn DSouza wrote:
>
> On Tue, Jul 31, 2012 at 4:41 PM, Andrew Fish <[email protected]> wrote:
>
>>
>> On Jul 31, 2012, at 4:32 PM, Melwyn DSouza wrote:
>>
>>
>>
>> On Mon, Jul 30, 2012 at 5:44 PM, Andrew Fish <[email protected]> wrote:
>>
>>>
>>> On Jul 30, 2012, at 4:49 PM, Melwyn DSouza wrote:
>>>
>>> I have an (yasm) asm file which i need to have it as a part of Module
>>> Application. It is of yasm file format,
>>> Yasm file format
>>> http://yasm.tortall.net/
>>>
>>>
>>> edk 2 build tools point to x86_amd64 format
>>>
>>> as seen in tools_def.txt
>>>
>>>
>>> DEFINE VS2010_BINX64 = DEF(VS2010_BIN)\x86_amd64
>>>
>>>
>>> ….
>>>
>>>
>>> *_VS2010_X64_ASM_PATH = DEF(VS2010_BINX64)\ml64.exe
>>>
>>>
>>> This points to which assembler to use. So try changing it to point to
>>> yasm?
>>>
>> Did that... by
>>
>> DEFINE YASM_BIN = C:\pathto\yasm\win32
>>
>> and
>>
>> # *_VS2010_X64_ASM_PATH = DEF(VS2010_BINX64)\ml64.exe Commented
>> because we use yasm format assembly files
>> *_VS2010_X64_ASM_PATH = DEF(YASM_BIN)\yasm.exe
>>
>> However when i compile my module using ...
>>
>> build -p DuetPkg\DuetPkgX64.dsc -m
>> MdeModulePkg\Application\MyApp\MyApp.inf
>>
>> It is still picking the <VS Path>\x86_amd64\ml64.exe
>>
>>
>> So did you update Conf/target.txt to set TOOL_CHAIN_TAG to VS2010? I
>> don't see a -t argument to build in your example.
>>
> below is the setting from the Conf/target.txt file...
>
> TOOL_CHAIN_TAG = VS2010x86
>
>
>>
>>
> VS2010x86 != VS2010
>
> *_VS2010x86_X64_ASM_PATH = DEF(VS2010x86_BINX64)\ml64.exe
>
> *_VS2010_X64_ASM_PATH = DEF(VS2010_BINX64)\ml64.exe
>
> The form of the variables is: TARGET_TOOLCHAIN_ARCH_COMMANDTYPE_ATTRIBUTE
>
Ok got it. that was the problem...
Now i am getting some error for
myworkspace\MdePkg\Library\BaseLib\X64\Thunk16.asm
it is trying to use yasm.exe to compile Thunk16.asm
Does Thunk16.asm follow a format compatible with yasm.exe?
Is there anyway to compile test1.asm from myapp module using yasm.exe
separately, without having to touch other packages/modules ....
I would like to selectively use yasm.exe to compile my module application
asm files...
Thanks,
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-buildtools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel
