Cross-compiling with a GCC-based compiler

[mtribiere]

I'm trying to compile with a in-house made compiler called ccppc. Here is my xmake.lua:

toolchain("myToolchain")

    set_kind("standalone")
    set_toolset("cc", "ccppc")
    set_toolset("ld", "ldppc")

toolchain_end()

target("TEST")
    set_kind("binary")
    add_files("src/command.c")

Then I do:

xmake f --toolchain=myToolchain
xmake -v

Here is the error I get:

checking for ccppc ... ok
checking for the c compiler (cc) ... ccppc
error: cannot find known tool script for ccppc

How can I use my compiler?

Setup

• XMake 2.7.8
• Windows 10
• Compiler ccppc (GCC-based)
• Linker ldppc (GCC-based)

Edit - More precise output

C:\Tools\DEV\TEST_PARTITION>..\xmake\xmake.exe f --toolchain=myToolchain -v -c
checking for platform ... windows
checking for architecture ... x64
checking for ldppc ... ok
checking for the linker (ld) ... ldppc
configure
{
    clean = true
    ccache = true
    host = windows
    mode = release
    plat = windows
    toolchain = myToolchain
    kind = static
    ndk_stdcxx = true
    buildir = build
    arch = x64
}

C:\Tools\DEV\TEST_PARTITION>..\xmake\xmake.exe -v
checking for ccppc ... ok
checking for the c compiler (cc) ... ccppc
error: ...mdir\core\sandbox\modules\import\core\base\scheduler.lua:56: cannot find known tool script for ccppc
stack traceback:
        @programdir\core\base\utils.lua:290: in function <@programdir\core\base\utils.lua:280>
        [C]: in function 'error'
        @programdir\core\base\os.lua:913: in function 'base/os.raiselevel'
        (...tail calls...)
        ...mdir\core\sandbox\modules\import\core\base\scheduler.lua:56: in field 'co_start_withopt'
        @programdir\modules\private\async\runjobs.lua:217: in function <@programdir\modules\private\async\runjobs.lua:162>
        [C]: in function 'xpcall'
        @programdir\core\base\utils.lua:280: in function 'sandbox/modules/utils.trycall'
        @programdir\core\base\scheduler.lua:520: in function 'base/scheduler.co_group_begin'
        ...mdir\core\sandbox\modules\import\core\base\scheduler.lua:94: in field 'co_group_begin'
        @programdir\modules\private\async\runjobs.lua:162: in function <@programdir\modules\private\async\runjobs.lua:56>
        (...tail calls...)
        @programdir\actions\build\build.lua:259: in function <@programdir\actions\build\build.lua:247>
        (...tail calls...)
        @programdir\actions\build\main.lua:109: in global '_do_build'
        @programdir\actions\build\main.lua:183: in function <@programdir\actions\build\main.lua:173>
        [C]: in function 'xpcall'
        @programdir\core\base\utils.lua:280: in function 'sandbox/modules/utils.trycall'
        @programdir\core\sandbox\modules\try.lua:117: in global 'try'
        @programdir\actions\build\main.lua:171: in function <@programdir\actions\build\main.lua:133>
        (...tail calls...)
        [C]: in function 'xpcall'
        @programdir\core\base\utils.lua:280: in function 'sandbox/modules/utils.trycall'
        (...tail calls...)
        @programdir\core\base\task.lua:501: in function 'base/task.run'
        @programdir\core\main.lua:300: in upvalue 'cotask'
        @programdir\core\base\scheduler.lua:404: in function <@programdir\core\base\scheduler.lua:397>

C:\Tools\DEV\TEST_PARTITION>

[waruqi]

    set_toolset("cc", "gcc@ccppc")
    set_toolset("ld", "g++@ccppc") -- ccppc++? do not use ld directly

[mtribiere]

Thanks I will try that in just a few. However, I really do need to use ldppc directly (it's a limitation of this custom compiler). Is it possible to do so ?

[mtribiere]

Alright it does work now however I have a new error:

C:\Tools\DEV\TEST_PARTITION>..\xmake\xmake.exe -v
checking for ccppc ... ok
checking for the c compiler (cc) ... ccppc
[ 25%]: cache compiling.release src\command.c
ccppc -c -fexceptions -o build\.objs\TEST\windows\x64\release\src\command.c.obj src\command.c
checking for ccppc ... ok
checking for flags (-MMD -MF) ... no
checking for flags (-fdiagnostics-color=always) ... no
checking for flags (-fcolor-diagnostics) ... no
error: ccppc tried to spawn C:\Tools\AH-Applications\WindRiver\gnu\3.3.2-vxworks653\x86-win32\bin\..\lib\gcc-lib\powerpc-wrs-vxworksae\3.3.2\get_feature.exe but failed: Invalid descriptor

C:\Tools\DEV\TEST_PARTITION>

[mtribiere]

A question about this last error, is the PATH of my command-line propagated to XMake build?