Skip to content

Commit ce097d2

Browse files
artus9033artus9033
committed
chore: deintegrate CLI docs
1 parent 86737d7 commit ce097d2

1 file changed

Lines changed: 0 additions & 44 deletions

File tree

‎docs/docs/docs/getting-started/quick-start.mdx‎

Lines changed: 0 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -32,50 +32,6 @@ The library will be automatically linked via autolinking.
3232

3333
First, we need to package our React Native app as an XCFramework or Fat-AAR.
3434

35-
#### With the built-in CLI
36-
37-
You can use the built-in CLI that comes with this library to package your React Native app for iOS and Android:
38-
39-
##### Publish for iOS
40-
41-
Simply run `npx brownfield package:ios` to create an XCFramework that you can later integrate into your native iOS app according to other instruction sections below.
42-
43-
Available arguments:
44-
45-
| Argument | Description | Default |
46-
| ----------------- | -------------------------------------------------------------------------------------------- | ------------------------ | ----- |
47-
| --configuration | Explicitly set the scheme configuration to use. This option is case sensitive. | |
48-
| --scheme | Explicitly set Xcode scheme to use | |
49-
| --target | Explicitly set Xcode target to use | |
50-
| --build-folder | Location for iOS build artifacts. Corresponds to Xcode's "-derivedDataPath". | "build" |
51-
| --sdk | The SDK to build for (iphoneos/iphonesimulator); to build for multiple, separate with commas | iphoneos,iphonesimulator |
52-
| --no-install-pods | Skip installing pods before building | |
53-
| --verbose | | Enable verbose logging | false |
54-
55-
##### Build for Android
56-
57-
To build the artifact for Android without publishing, run `npx brownfield package:aar --module-name app`.
58-
59-
Available arguments:
60-
61-
| Argument | Description | Default |
62-
| ------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ----- |
63-
| --variant | Specify your app's build variant, which is constructed from build type and product flavor, e.g. 'debug' or 'freeRelease'. | 'debug' |
64-
| --module-name | AAR module name | '' (root project) |
65-
| --verbose | | Enable verbose logging | false |
66-
67-
##### Publish locally for Android
68-
69-
To publish the `.aar`(s) built beforehand with `react-native-brownfield package:aar` to Maven local, which will allow Gradle to be able to load it from Maven local repository, run:
70-
71-
`npx brownfield publish:android --module-name app`
72-
73-
| Argument | Description | Default |
74-
| ------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ----- |
75-
| --variant | Specify your app's build variant, which is constructed from build type and product flavor, e.g. 'debug' or 'freeRelease'. | 'debug' |
76-
| --module-name | AAR module name | '' (root project) |
77-
| --verbose | | Enable verbose logging | false |
78-
7935
#### With Rock
8036

8137
It is very likely you will find Rock the easiest way to use brownfield in your React Native project. Rock provides for instance a clean template with `@callstack/react-native-brownfield` already integrated so you can easily bootstrap a new, clean brownfield project with zero manual configuration required. Below you will find instructions both for bootstrapping a new brownfield project and integrating your existing React Native app with Rock.

0 commit comments

Comments
 (0)