target-level dependencies to non-existent target

[binkinator]

I was getting something like this while trying to use the VitaSDK to compile homebrew:

CMake Error at CMakeLists.txt:93 (add_dependencies):
Cannot add target-level dependencies to non-existent target "reVita.skprx".

The add_dependencies works for top-level logical targets created by the
add_executable, add_library, or add_custom_target commands. If you want to
add file-level dependencies see the DEPENDS option of the add_custom_target
and add_custom_command commands.

I found a discussion about it on the HENkaku discord where someone suggested simply removing the offending add_dependencies line mentioned in the error.

I did just that and...it worked!

Not sure if this is the right way to do it but I'm finally able to compile things cleanly so there's that.

If anyone has a better suggestion please let me know!

 

[godreborn]

I just tried to build this (had success with taihen.skprx), but this is what happens:

godreborn@GODREBORN-LAPTOP:~/ds34vita/build$ cd ../..
godreborn@GODREBORN-LAPTOP:~$ cd reVita/build
godreborn@GODREBORN-LAPTOP:~/reVita/build$ make install
[ 80%] Built target reVita
[ 82%] Building stubs stubs
[ 84%] Built target stubs
[ 84%] Built target libreVita_stub_weak.a
[ 84%] Built target libreVita_stub.a
[ 88%] Built target reVita.skprx
[ 91%] Linking C executable reVitaMotion
/usr/local/vitasdk/bin/../lib/gcc/arm-vita-eabi/10.3.0/../../../../arm-vita-eabi/bin/ld: cannot find -lreVita_stub
collect2: error: ld returned 1 exit status
make[2]: *** [reVitaMotion/CMakeFiles/reVitaMotion.dir/build.make:118: reVitaMotion/reVitaMotion] Error 1
make[1]: *** [CMakeFiles/Makefile2:306: reVitaMotion/CMakeFiles/reVitaMotion.dir/all] Error 2
make: *** [Makefile:149: all] Error 2

 

[godreborn]

nm, I was doing it wrong. the error you mentioned didn't happen to me:

 

[binkinator]

nm, I was doing it wrong. the error you mentioned didn't happen to me:

View attachment 317532

I want mine to “just work” too. Responded on discord…

 

[godreborn]

it would not compile until I updated vitasdk. maybe that will work for you?

 

[binkinator]

it would not compile until I updated vitasdk. maybe that will work for you?

I have what I believe to be the latest (I’m new to the Vita stack.) I followed these instructions: https://vitasdk.org/

On discord they say that you have to remove the add_dependencies or add the -self suffix if you’re on cmake 3.20+.
I’m on 3.22.

What version of cmake are you on?

 

[godreborn]

Cmake --version ?

 

[binkinator]

Cmake --version ?

Indeed:

wwiii@wwiii-VAIO MSYS ~/projects/sixaxis
$ cmake --version
cmake version 3.22.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

 

[godreborn]

okay, it's 3.18.4.

 

[godreborn]

Indeed:

wwiii@wwiii-VAIO MSYS ~/projects/sixaxis
$ cmake --version
cmake version 3.22.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

off topic, but since you compiled atmosphere, I assume you have devkitpro installed. I'm having this issue with devkitpro, and it's the only computer problem left that I can't figure out what the hell is wrong:

https://gbatemp.net/threads/problem-with-apt-update-in-debian.615217/#post-9878166

I've tried manually adding in the key, but the key doesn't seem to exist whatsoever.

 

[binkinator]

okay, it's 3.18.4.

That's it! Thank you for confirming.

You are below 3.20 so you don't get the weirdness that is: add_dependencies

I was able to work around it with the -self suffix (or removing the line altogether.)

 

[binkinator]

off topic, but since you compiled atmosphere, I assume you have devkitpro installed. I'm having this issue with devkitpro, and it's the only computer problem left that I can't figure out what the hell is wrong:

https://gbatemp.net/threads/problem-with-apt-update-in-debian.615217/#post-9878166

I've tried manually adding in the key, but the key doesn't seem to exist whatsoever.

will certainly take a look.

The key should be bundled. See if this matches your situation:

https://devkitpro.org/viewtopic.php?f=15&t=9234

 

[godreborn]

That cmake may be the newest for the Debian build I'm using. What distro are you using?

 

[binkinator]

That cmake may be the newest for the Debian build I'm using. What distro are you using?

I'm currently on:

• Windows 10
• msys2

 

[godreborn]

I'm using wsl.

 

[godreborn]

I installed devkitpro on msys2, and I installed cmake. it's the same version as yours. you might try Debian if you don't want to commit out that line:

 

[binkinator]

I installed devkitpro on msys2, and I installed cmake. it's the same version as yours. you might try Debian if you don't want to commit out that line:

View attachment 317708

Thanks for taking the journey with me! I think we both understand a little more than when we started. I’m actually at peace with removing/modifying the code now that I know it‘s just a feature of cmake moving on and our PSVITA code base being a little stagnant in many cases. It was the unknown that was buggin me! Thanks again!

 

[godreborn]

there was a line in ds4vita iirc that will not compile, gives a coding error, which I think is related to the vitasdk being too new. removing the line compiles it. it's in main.c. in almost all cases, when you get a coding error, it's either missing dependencies or something is the wrong version. dependencies usually give you a file or directory not found error, but not always.

 

[godreborn]

will certainly take a look.

The key should be bundled. See if this matches your situation:

https://devkitpro.org/viewtopic.php?f=15&t=9234

I fixed the problem several days ago. I just took the gpg key for devkitpro on Ubuntu and injected it into Debian, then removed the nonexistent servers, since some didn't seem to exist at all, beyond bullseye release.

Also, what I was going to ask you is if you knew if you could downgrade vita sdk?

 

[binkinator]

I fixed the problem several days ago. I just took the gpg key for devkitpro on Ubuntu and injected it into Debian, then removed the nonexistent servers, since some didn't seem to exist at all, beyond bullseye release.

Also, what I was going to ask you is if you knew if you could downgrade vita sdk?

Glad you’re sorted. :-)

The easiest was I can think of would be to run rm -rf $VITASDK and then git pull an earlier revision of https://github.com/vitasdk/vdpm and reinstall.