Git Product home page Git Product logo

Comments (4)

mikezackles avatar mikezackles commented on May 18, 2024

Current status:

I did a good bit of work on this on this branch, which also includes work related to #25 and #19.

I now have a more targeted branch intended to focus on just the build. This branch also includes the fixes in #8 and #23 as they are necessary to build without ignoring compiler warnings. More detailed docs will follow, but the magmad.so build is now intended to run in its own folder so that build artifacts don't get mingled with the sources and patches that live in lib.

The autotools build is intended to be as simple as possible as a starting point. It builds a static magma library that is linked against the entry point in magma.c, and the same library links against the test executable.

Currently I am able to build magmad.so, the magma daemon, and the tests on my local Arch install, and I can run the tests with no failures.

I still need to define and document what additional capabilities are necessary to achieve feature parity with the eclipse/VM environment (e.g., testing with valgrind).

from magma.

mikezackles avatar mikezackles commented on May 18, 2024

Also note that the symbols table for symbols defined in magmad.so has changed. Since I'm sharing a static library for the daemon and the tests, and magma.c includes magma.h (and hence symbols.h), I get multiple definition issues on link (even with __attribute__((common))). Same story for the tests. I've changed symbols.h so that they're declared as extern (without __attribute__((common))), and they're now defined/initialized in symbols.c. Please let me know if there are issues with this approach -- I'm aware that it does result in more boilerplate, but the other approach seems to make it pretty difficult to split the build up.

from magma.

kenthawk avatar kenthawk commented on May 18, 2024

Short of getting with Ladar on this, I'm not sure how we'd know. Maybe we start with a fresh VM, build using eclipse with access to your branch and see if removing ((common)) has some side effects on the build or console compiler warning output. Don't know.

from magma.

kenthawk avatar kenthawk commented on May 18, 2024

The build has been migrated to autotools thanks to Zach's large body of work. All of this work now lives on the develop branch.

from magma.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.