NotificationsYou must be signed in to change notification settings
Fork3
Star9

Commite0da7a7

committed

Jamfile: Optimize build output size

The goal here is to keep builds reasonably fast for development.Some time hopefully we'll have the ability to specify whether to builda debug or release build. But for now, we're stuck with trying tooptimize both build time and build size simultaneously.Coolcoder613eb proposed four build flags to add. I tested them fortheir effect on build time and size.

1 parenteab0d76 commite0da7a7Copy full SHA for e0da7a7

File tree

1 file changed

-1

lines changed

Jamfile

1 file changed

-1

lines changed

`‎Jamfile‎`

Lines changed: 3 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -82,7 +82,9 @@ SubDirHdrs /system/lib/python$(python_version)/vendor-packages/pybind11/include/`
`82`	`82`	`SubDirHdrs /system/develop/headers/python$(python_version)/ ;`
`83`	`83`
`84`	`84`	`# Additional C++ flags to use when compiling`
`85`		`-SubDirC++Flags -std=c++14 -pipe -fPIC ;`
	`85`	`+# TODO: only run -Os for release builds. Development builds should prioritize`
	`86`	`+# build time`
	`87`	`+SubDirC++Flags -std=c++14 -pipe -fPIC -Os -fvisibility=hidden ;`
`86`	`88`
`87`	`89`	`# Flags to use when linking`
`88`	`90`	`LINKLIBS = -lbe ;`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commite0da7a7

File tree

1 file changed

1 file changed

`‎Jamfile‎`

0 commit comments