Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: add pre-build configure or cmake for local configuration and other benefits #19

Closed
derekbruening opened this issue Nov 27, 2014 · 2 comments

Comments

@derekbruening
Copy link
Contributor

From [email protected] on February 16, 2009 14:42:31

split from issue #2 : see notes there on why we never needed this for past
proprietary products

I would lean toward CMake instead of autoconf http://www.cmake.org/ We could achieve the following with cmake:

  1. configure build for local toolchain tools: currently we have some checks
    for -T vs -dT, gcc -fvisibility, etc., but we don't build on RHEL3
    ( issue build: automatically work around typedef conflicts #18 ) due to typedef conflicts, and in the future if we port to
    other platforms we'll want to add more features like HAVE_PROC_MAPS.

  2. add dependencies back in to core/ (USEDEP=0 right now due to "make
    clear" bugs with the .dep files: PR 207890, PR 214218)

  3. build in parallel (PR 209902)

  4. reduce Windows building time due to cygpath invocations: move them all
    to configure time

  5. possibly: hook our tests up to the cmake-integrated CTest and CDash
    plaform-independent regression testing and reporting engine?

Some issues:

  • devs have to install cmake
    but, available on yum, apt-get repos so painless on linux
  • not clear cmake will support our mix of cygwin paths but microsoft compiler

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=19

@derekbruening
Copy link
Contributor Author

From [email protected] on February 18, 2009 20:14:55

More notes on what the configure should do:

  • Have the configure step check if a local gnu as is sufficient (esp on
    64-bit that can't run 32-bit binary).
  • Change default ARCH based on platform

@derekbruening
Copy link
Contributor Author

From [email protected] on March 03, 2009 16:56:18

revision 64 put in cmake support for core, api/docs, libutil, tools, and tools/DRgui
with a massive rewrite of build rules from Makefiles to cmake revision 65 updated HowToBuild .wiki

there are many missing pieces for developers, but the bulk of it is there

not yet finished: issue #65 : build: convert suite/ to cmake and ctest issue #63 : packaging to replace makezip.sh issue #67 : api/samples/Makefile issue #64 : "make review" issue #66 : "make runregression" + internal build# issue #73 : provide automatic suport for locating ml64.exe when using Vista SDK+WDK

future nice-to-have work: issue #68 : replace perl with cmake scripts and CTest issue #69 : re-add support for core unit tests and standalone build rules issue #70 : symbol store support in core/Makefile and tools/Makefile issue #71 : support mingw/cygwin makefile cmake target with cl compiler, for make -j

Status: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant