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.

Sign up for GitHub

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

Jump to bottom

How far along is ocp-build? #7

Open
bluddy opened this issue Mar 3, 2016 · 1 comment
Open

How far along is ocp-build? #7

bluddy opened this issue Mar 3, 2016 · 1 comment

Comments

@bluddy
Copy link

bluddy commented Mar 3, 2016

I'm looking for an easy to use, cross-platform build tool.

  1. How far along is ocp-build?
  2. Is there any way to avoid specifying every file?
  3. Why is the manual so incomplete?
@lefessan
Copy link
Member

  1. I have been using ocp-build in production for the last 5 years without too many problems
  2. No, the whole philosophy behind ocp-build is that developers should always specify all the sources, because it makes it easier for other devs (or themselves a few months later) to understand the architecture of the project.
  3. Not yet have had time to write the missing parts...

ghost pushed a commit to facebook/flow that referenced this issue Jun 16, 2016
@gabelevi
Fix ocp-build build for Flow
cee764e 
Summary:
A lot needed to change in this diff.

1. ocp-build by design forces you to list out every file (OCamlPro/ocp-build#7 (comment)). These lists were out of date, so I started again from scratch and modeled it after our internal buck build configs.
2. Listing every file explicitly made this build system super fragile. Since most people are developing with ocamlbuild and buck, it would break. So I added a preprocessor that supports some globbing
3. Flow doesn't copy every hack file into the `hack/` directory, which means we can't just reuse hack's ocp-build file. They'll need their own (future work)
4. `Makefile` is used by Linux and OS X to run ocp-build. `make.bat` is used by Windows.

Reviewed By: samwgoldman

Differential Revision: D3432129

fbshipit-source-id: b0b19b0bf1f5fb1f77190f751e2215ea41d7aff3
hhvm-bot pushed a commit to facebook/hhvm that referenced this issue Jun 16, 2016
@gabelevi
Fix ocp-build build for Flow
e6be6ad 
Summary:
A lot needed to change in this diff.

1. ocp-build by design forces you to list out every file (OCamlPro/ocp-build#7 (comment)). These lists were out of date, so I started again from scratch and modeled it after our internal buck build configs.
2. Listing every file explicitly made this build system super fragile. Since most people are developing with ocamlbuild and buck, it would break. So I added a preprocessor that supports some globbing
3. Flow doesn't copy every hack file into the `hack/` directory, which means we can't just reuse hack's ocp-build file. They'll need their own (future work)
4. `Makefile` is used by Linux and OS X to run ocp-build. `make.bat` is used by Windows.

Reviewed By: samwgoldman

Differential Revision: D3432129

fbshipit-source-id: b0b19b0bf1f5fb1f77190f751e2215ea41d7aff3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bluddy @lefessan