Home » Premake » Forums » Premake Cookbook

newplatform()

annulen | 01 Jul 2011

This function allows to define new platform in your project for cross-compilation with GCC:

function newplatform(plf)
    local name = plf.name
    local description = plf.description
 
    -- Register new platform
    premake.platforms[name] = {
        cfgsuffix = "_"..name,
        iscrosscompiler = true
    }
 
    -- Allow use of new platform in --platfroms
    table.insert(premake.option.list["platform"].allowed, { name, description })
    table.insert(premake.fields.platforms.allowed, name)
 
    -- Add compiler support
    -- gcc
    premake.gcc.platforms[name] = plf.gcc
    --other compilers (?)
end
 
function newgcctoolchain(toolchain)
    newplatform {
        name = toolchain.name,
        description = toolchain.description,
        gcc = {
            cc = toolchain.prefix .. "gcc",
            cxx = toolchain.prefix .. "g++",
            ar = toolchain.prefix .. "ar",
            cppflags = "-MMD " .. toolchain.cppflags
        }
    }
end

Example usage:

newplatform {
    name = "amino110",
    description = "Amino 110",
    gcc = {
        cc = "/opt/hardhat/devkit/ppc/405/bin/ppc_405-gcc",
        cxx = "/opt/hardhat/devkit/ppc/405/bin/ppc_405-g++",
        cppflags = "-MMD -DAMINO_110"
    }
}
 
newgcctoolchain {
    name = "amino110",
    description = "Amino 110",
    prefix = "/opt/hardhat/devkit/ppc/405/bin/ppc_405-",
    cppflags = "-DAMINO_110"
}
‹ Chaining actions Pc-lint 8 postbuildcommand ›
starkos | 26 Oct 2011 14:17

Can you submit this as a patch? Would be handy to have.

annulen | 26 Oct 2011 16:56

It has a dirty hack inside (at least in my opinion):

premake.fields["platforms"].allowed = table.keys(premake.platforms)

it overwrites list of allowed platforms for "platform" option declared in cmdline.lua. Otherwise new platform name won't pass validatation.

annulen | 31 Oct 2011 17:57

Or it's fine for you?

starkos | 01 Nov 2011 12:59

Can you table.insert() the new value instead?

Anonymous | 10 Nov 2011 19:56

this doesn't seem to work for codeblocks.

gmake generator generates a couple more configs with the name "xxxxx_amino110" which are not in codeblocks or codelite projects.

Anonymous | 10 Nov 2011 20:00

how to add platform specific defines?

annulen | 10 Nov 2011 20:25

>how to add platform specific defines?

To add platform define for everything, just add it to cppflags of gcc. But you can also use 

configuration "platformname"

inside any project/solution

annulen | 13 Nov 2011 19:14

@starkos: It works. I've updated function definition, and added separate version of function for "platforms" which are defined by standard gcc (cross-)toolchain.

annulen | 16 Nov 2011 07:40

Or maybe something like this instead of newgcctoolchain:

newplatform {
    name = "amino110",
    description = "Amino 110",
    gcc = newgcc("/opt/hardhat/devkit/ppc/405/bin/ppc_405-"),
    extracppflags = "-DAMINO_110"
}
annulen | 25 Nov 2011 17:08

@starkos: As for patch, I'm in doubt in which file should I place these functions (api.lua?). Feel free to copy and paste it where you like :)

Anonymous | 20 Jan 2012 22:10

How do I include platform specific files?

annulen | 21 Jan 2012 10:51

For example, this way:

project "A"
  -- Configuration goes
  files {
    -- files for all platforms
  }
  if _OPTIONS.platform == "someplatform" then
    files {
   -- platform-specific files
    }
  end

Platform-specific files will be built if you call premake4 with --platform=somelpatform option.