LINK : fatal error LNK1189: library limit of 65535 objects exceeded

[Alice-Cheshire]

Bevy version

0.4.0 (3b2c6ce)

Operating system & version

Windows 10 64-bit (version 1709)

What you did

I was just following the setup instructions here. When I tried to follow the cargo run --features bevy/dynamic step things seem to have gone awry though.

What actually happened

Got a linker error from bevy_dylib with this error code:

LINK : fatal error LNK1189: library limit of 65535 objects exceeded

error: aborting due to previous error

error: could not compile `bevy_dylib`

Additional information

This is my first time messing with Rust and I'm not at all familiar with this kind of toolchain so there could very easily be something I'm doing wrong but I was just following the directions on the getting started/setup page so I'm not sure what I would have done wrong here. Looking around I've found old issues saying to try rustflags = ["-Zshare-generics=y"] but I have absolutely no idea where to put this and searching around is frustratingly unhelpful since every mention I can find of it it just someone telling someone to try it. Putting it in my project's cargo.toml seems to do nothing. I seem to have been able to accomplish the other steps on that page that come after without issue though. I did the LLD linker bit as well as the nightly Rust compiler bit and adding bevy in my cargo.toml dependencies. I also seem to have accomplished the copy+paste of code on the getting-started/apps and up to "Your First System" bit on getting-started/ecs so I'm not sure if this issue is something I have to worry about or not before continuing.

[fopsdev]

same here...
its an issue with the MSVC-based toolchain
maybe not using the the msvc-toolchain could solve it... but not sure what to use on windowes then

[cart]

Looks like a duplicate of #832

[Alice-Cheshire]

Looks like a duplicate of #832

I'm not certain if it is since the stuff in the first post of that issue doesn't happen to me but regardless, the solutions in that issue don't seem to actually fix the problem for me unfortunately. It doesn't help that it's not clear on where this part belongs:

[target.x86_64-pc-windows-msvc]
rustflags = ["-Zshare-generics=off"]

It mentions a path called /.cargo/.config but I'm not seeing a .cargo folder anywhere. (I do have hidden files shown for reference.) In other places I found this same suggestion they mention cargo.toml but when I try adding that there I get this warning which suggests this isn't actually where it belongs:

warning: unused manifest key: target.x86_64-pc-windows-msvc.linker
warning: unused manifest key: target.x86_64-pc-windows-msvc.rustflags

After looking through Rust and Cargo docs and various issues and posts on forums, I can't figure out where this stuff belongs if not in cargo.toml as suggested in some of the issues.

[Cupnfish]

.
├── .cargo
│   └── config.toml
├── .gitignore
├── Cargo.lock
├── Cargo.toml
└── src
    └── main.rs

You can try this again, this is a normal bevy project, and you need create a folder called .cargo with the config.toml.
And then use cargo clean and cargo run to build your project.

[Cupnfish]

#832 (comment)
I followed this method to try to compile, and solved my problem. My config.toml Now Looks Like This:

[target.x86_64-pc-windows-msvc]
linker = "rust-lld.exe"
rustflags = ["-Zshare-generics=off"]

[Alice-Cheshire]

.
├── .cargo
│   └── config.toml
├── .gitignore
├── Cargo.lock
├── Cargo.toml
└── src
    └── main.rs

You can try this again, this is a normal bevy project, and you need create a folder called .cargo with the config.toml.
And then use cargo clean and cargo run to build your project.

Is it supposed to be just cargo run or cargo run --features bevy/dynamic like it says on book/getting-started/setup? Trying the latter did have a change this time around. I got this error instead:

= note: rust-lld: error: undefined symbol: __CxxFrameHandler4
>>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$??$_Emplace_reallocate@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@?$vector@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@v?$allocator@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@2@@std@@QEAAPEAV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@1@QEAV21@$$QEAV21@@z)
>>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$??$_Emplace_reallocate@AEBV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@?$vector@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@v?$allocator@V?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@@2@@std@@QEAAPEAV?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@1@QEAV21@AEBV21@@z)
>>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$?newIncludeResult@DirStackFileIncluder@@MEBAPEAUIncludeResult@Includer@TShader@glslang@@aebv?$basic_string@DU?$char_traits@D@std@@v?$allocator@D@2@@std@@aeav?$basic_ifstream@DU?$char_traits@D@std@@@7@H@Z)
>>> referenced 453 more times

     rust-lld: error: undefined symbol: __GSHandlerCheck_EH4
     >>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$?readLocalPath@DirStackFileIncluder@@MEAAPEAUIncludeResult@Includer@TShader@glslang@@PEBD0H@Z)
     >>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$?getDirectory@DirStackFileIncluder@@MEBA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V23@@Z)
     >>> referenced by glslang.glsltospirv.lib(glslang_c_interface.obj):($unwind$?uflow@?$basic_filebuf@DU?$char_traits@D@std@@@std@@MEAAHXZ)
     >>> referenced 297 more times

error: aborting due to previous error
error: could not compile bevy_dylib

I also ran into one other unforeseen issue. Apparently Windows doesn't allow you to simply name a folder .cargo. Instead you need to name it .cargo. and it will then remove the second dot at the end. This isn't something I'd ever actually come across myself so it was rather confusing, albeit easy to find info on.

[Cupnfish]

https://github.com/rgripper/game-temp-1
You can see my game temp...
It's .cargo, not .cargo..
this repository hasn't modified .cargo/config.toml, you can use that before I say to modify it.

[Cupnfish]

About features, I always set it in Cargo.toml, example:

bevy = { version = "0.4", features = [ "dynamic"] }

Or you clould use cargo run --features bevy/dynamic to run it.
This is written by my mobile phone, cloud have any errors, but you can imitate this.

[Alice-Cheshire]

https://github.com/rgripper/game-temp-1
You can see my game temp...
It's .cargo, not .cargo..
this repository hasn't modified .cargo/config.toml, you can use that before I say to modify it.

If you just go with .cargo in Windows (apparently through Explorer but not through Command Prompt from what I've gathered), this is what happens. If you name it .cargo. though, for some reason Windows considers it a valid filename and it removes the second dot from the path. A few references on this: Link 1, Link 2

Edit: Finally found something directly addressing why it happens here. It happens because Windows considers it a file with an extension but no name. The second dot seems to be a workaround added in Windows 7 from what I've gathered.

About features, I always set it in Cargo.toml, example:

bevy = { version = "0.4", features = [ "dynamic"] }

Or you clould use cargo run --features bevy/dynamic to run it.
This is written by my mobile phone, cloud have any errors, but you can imitate this.

That seems like it'd be easier, at least if I can solve this issue I'm having with using bevy/dynamic in the first place.

[Cupnfish]

I’m not using Windows 7, But I found out that Windows 7 doesn’t allow you to create folders that start with a dot, but you can do that with Cmd:

mkdir .cargo

Or, you can just git clone my repository and see if it runs on your computer...

[Alice-Cheshire]

I’m not using Windows 7, But I found out that Windows 7 doesn’t allow you to create folders that start with a dot, but you can do that with Cmd:

mkdir .cargo

Or, you can just git clone my repository and see if it runs on your computer...

I'm not sure you're understanding what I'm saying. I've provided a solution to the folder naming problem on multiple occasions now so cloning your repository is pointless. To quote myself:

If you name it .cargo. though, for some reason Windows considers it a valid filename and it removes the second dot from the path.

As the second half of this sentence states, naming a folder .cargo. through Windows explorer creates a folder named just .cargo without issue. I'm honestly not sure what about that isn't coming across in what I'm saying.

[Alice-Cheshire]

To address the original problem the issue was opened for, changing rustflags = ["-Zshare-generics=y"] to rustflags = ["-Zshare-generics=off"] as @Cupnfish suggest in issue #1126 (which I'd thought I'd tried since creating .cargo/config.toml) looks to fix the original error.

The documentation for setting Bevy up could definitely do with explicitly saying where to put things like the rustflags line as well as probably addressing how to create a folder that starts with a dot in Windows in order to be more clear for people who haven't really used Rust or this kind of setup before.