Revision history [back]

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"? What are the outputs on the console?

Anyway, the command should be catkin_make with an underscore instead of a space. That said, I see two possible reasons:

• As @gvdhoorn said in the comment, it could be possible that a blacklist has been set. To revert to original settings, run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"? What are the outputs on the console?

Anyway, the command should be catkin_make with an underscore instead of a space. That said, I see two possible reasons:

• As @gvdhoorn said in the comment, it could be possible that a blacklist has been set. To revert to original settings, run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. That said, I see two possible reasons:

• As @gvdhoorn said in the comment, it could be possible that a blacklist has been set. To revert to original settings, run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. That said, I see two possible reasons:

• As @gvdhoorn said in the comment, it could be possible that a blacklist has could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. That said, If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki

• Pay attention to any possible CATKIN_IGNORE CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES="". More about this on the official wiki.

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.single-package.

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES="".

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package.

Extra infos sources about catkin_make whitelists/blacklists and CATKIN_IGNORE

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES=""

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package. If the package that contains the program you wrote has this kind of file in its root, delete it and repeat catkin_make

Extra infos sources about catkin_make whitelists/blacklists and CATKIN_IGNORE

Hi Juliette,

I work on a collaborative project, and it seems that a previous student working on this project has locked the "catkin make" command

That doesn't sound right to me. What do you mean by "locked"?

Anyway, the command should be catkin_make with an underscore instead of a space. If that doesn't solve your issue, I see two possible reasons:

• As @gvdhoorn said in the comment, a blacklist could have been set. I'm not sure if this setting is saved in the workspace or in the local PC of each user. To revert to original settings, try to run catkin_make -DCATKIN_WHITELIST_PACKAGES=""

• Pay attention to any possible CATKIN_IGNORE files in the root of the package. Those files (without any extension) are used to ignore the package from being built, kinda like a .gitignore but single-package. rule on a .gitignore file. If the package that contains the program you wrote has this kind of file in its root, delete it and repeat catkin_make

Extra infos sources about catkin_make whitelists/blacklists and CATKIN_IGNORE