Look into removing autogen from the build

Open
  • Is something wrong?
#303 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, python
Domain
build-system

Research direction

Start by tracing how TimeIndexPolicy and the dynamic BasketInfo struct are generated for the C++ build, and review the cross-compiling context in issue #264. Determine whether these types can be defined in C++ and exposed to Python without autogen. Done means the generation path is removed or simplified while the CSP engine still builds and cross-compiles.

Written by the indexing model from the issue text.

Description

part: build type: enhancement

Currently there are only two items generated to build csp engine

  • TimeIndexPolicy
  • dynamic BasketInfo struct

this complicated the build immensely, and also blocks us from cross compiling: https://github.com/Point72/csp/issues/264

We should see if there is a nice way to define these types in C++ and expose them to python, rather than define them in python and autogen c++

Dominant language
Python
Stars
450
Forks
91
Avg merge
18h 8m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Point72/csp

All issues in Point72/csp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.